Re: Shadow set problem finally solved

On Mar 13, 8:33 am, tadamsmar <tadams...@xxxxxxxxx> wrote:
On Mar 12, 9:08 pm, BEGINcornel...@xxxxxxxxxxxxxxxx (George Cornelius)
wrote:





In article <10b5d716-18aa-4705-bec3-dc169725a...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, tadamsmar <tadams...@xxxxxxxxx> writes:

On Mar 8, 5:22pm, George Cornelius wrote:
This thing really seems to be going nowhere. It sure seems to me that
this is a standard, pure-vanilla problem of a shadow set having a forced
error that VMS replicates on every shadow copy, something that's been
around since Phase I shadowing and RA series drives.

If that is the case, the solution is to overwrite the block in question.

You should, just to be thorough, examine [000000]BADBLK.SYS and if it
has any allocation, check its LBN's with $ DUMP/HEADER/BLOCK=C:0 .
[...] you can also do this:

$ create/fdl=sys$input JUNK.TMP001
area 0;allocation 1;contig yes;exact_positioning yes;position logical -
 16578125
<terminate with CTRL/Z>

[...]

How do I look at BADBLK.SYS for a shadow set?

I supplied a $ DUMP command.  But, never mind.  I only mentioned it for
thoroughness.  We already know in your case that the block is not allocated
anywhere.

How about doing this:

1.  Break out a member.
2.  Do an back/image on the member
3.  init/eras the member
4.  restore the image on the member
5.  boot on the member, making it the only member of the shadowset.
6.  merge the other disk into the shadowset

Yes, and if not a boot disk the following [after being certain nothing will be
writing to DSAn] would be more direct:

 $ dismount member2
 $ initialize/erase/system member2: dummy ! No special init command needed
 $ mount/foreign/noassist/override=shadow_membership member2
 $ backup/image/noalias DSAn: member2: ! Default init params are from source vol
 $ dismount DSAn:
 $ dismount member2:
 $ mount/sys DSAn:/shadow=member2:/conf label ! /conf just in case .-2 failed
 $ ! <add 2nd member later>

Even if it is a boot disk you may be able to do the above steps by booting
from CDROM.

My temp file technique solves the problem outright. There are no mounts and
dismounts; nor are there shadow copies.

Since it uses VMS to allocate the LBN into a temp file, it does not allocate
the LBN unless it is free.  This means you do not have to worry that it can
destroy data in some random file.

Would that get rid of all these parity errors?

Both approaches do this.  One is surgical; the other brute force.

It seems a little safer and easier (for me) than trying to write
blocks to specific LBAs.

Go for it.

It worked!  I finally got a clean ANAL/DISK/SHADOW!

Opps, not quite there. It ran clean on the single disk. But when I
add the other disk to the shadowset it reported the 4 blocks with
errors. VMS does not want to give these up without a fight.

I'm am going to init/erase that disk.

I am going to get a real sense of accomplisment when I finally see
those two zeros in the error count column of SHOW DEV D.


You seem to be a bit over your head here, and a procedure you
understand is much better than one that confuses you further.

Yes.  I was a bit nervous about trying to wipe out four blocks even
with the indications that they were not in a file.  And I could have
made a mistake.

I already had a command procedure for disk compression and all I had
to do was add an image/erase to it.

The one drawback to this procedure is that you have to refrain from
working on the computer till it completes, or at least be prepared to
copy your work off to a safe place.  The system was up, but the system
disk was destined to be overwritten.

If I just zapped the four blocks I could have avoided this.- Hide quoted text -

- Show quoted text -

.

Relevant Pages

  • Re: Sizing up Disks with Shadowing
    ... Not as soon as the initial shadow copy is ready at least, ... the master. ... member being added to a 2 member set), data is read from either of the two ... place without the need to lock disk blocks or block I/O, ...
    (comp.os.vms)
  • Re: Sizing up Disks with Shadowing
    ... Not as soon as the initial shadow copy is ready at least, ... A "master" member of a shadowset is only meaningful during a merge ... place without the need to lock disk blocks or block I/O, ...
    (comp.os.vms)
  • Re: physical drive replacement
    ... >> My first problem is determining which of the 2 physical drives in stripeset ... DELETE the disk, quiesce the bus and perform the physical swap, ... > and mount it into the shadow set, which should trigger a shadow copy ...
    (comp.os.vms)
  • Re: Shadow Volume Copy
    ... set member must it consider as master,... ... describe a member as "master" is pretty much meaningless. ... No, in a merge, one disk is read (which one is determined by queue ... disk in a shadow set will be its "master". ...
    (comp.os.vms)
  • Re: Implementing a RAID 1 Array
    ... For your RAID 1 drive is hardware RAID 1, you will not see the mirrored ... drive in the Disk Management console. ... The Volume Shadow Copy Service provides the backup infrastructure for the ...
    (microsoft.public.windows.server.sbs)