[Info-vax] analyze/disk errors

[tadamsmar]

On Thursday, December 5, 2013 11:16:49 AM UTC-5, tadamsmar wrote:
> On Thursday, December 5, 2013 7:55:23 AM UTC-5, Stephen Hoffman wrote:
> 
> > On 2013-12-04 20:29:53 +0000, tadamsmar said:
> 
> > 
> 
> > 
> 
> > 
> 
> > > Note that I did not copy any [000000].  I tried to copy BADBLK.SYS, but 
> 
> > 
> 
> > > I got an error on the copy command and did not copy it.
> 
> > 
> 
> > ...
> 
> > 
> 
> > >  If the disk were used non-shadowed, then I could just repopulate 
> 
> > 
> 
> > > BADBLK.SYS anyway.
> 
> > 
> 
> > 
> 
> > 
> 
> > I'm quite curious here, as all of what's above would seem 
> 
> > 
> 
> > counterintuitive.  There's also some wrong information above, too.
> 
> > 
> 
> > 
> 
> > 
> 
> > Why are you messing with BADBLK.SYS?
> 
> > 
> 
> > 
> 
> > 
> 
> > What do you think the BADBLK.SYS file is doing (and why are you trying 
> 
> > 
> 
> > to copy or restore it)?
> 
> > 
> 
> > 
> 
> > 
> 
> > Also AFAIK, while HBVS isn't accessing the BADBLK.SYS file as HBVS 
> 
> > 
> 
> > doesn't know from file systems, that file is active and is used by file 
> 
> > 
> 
> > systems on HBVS volumes.
> 
> > 
> 
> > 
> 
> > 
> 
> > You're easily one of the most creative folks working with VMS, and your 
> 
> > 
> 
> > approaches certainly seem to slam into doc errors or confusions all 
> 
> > 
> 
> > over.  In the old days, I'd look to get you into a field test, but 
> 
> > 
> 
> > that's fodder for another day.
> 
> > 
> 
> > 
> 
> > 
> 
> > 
> 
> > 
> 
> > -- 
> 
> > 
> 
> > Pure Personal Opinion | HoffmanLabs LLC
> 
> 
> 
> I was just trying to clear up some ANAL/DISK errors.
> 
> 
> 
> ANAL/DISK gave me a this warning ANALDISK-W-MAPAREA on BADBLK.SYS and some other files.
> 
> 
> 
> HELP/MESS says to try copying the file to address this warning.  So I tried to do copy it.  Copying worked on the other files, but I got an error when I tried to copy BADBLK.SYS.  So I made an image backup and restored the image from that backup and that cleared up the warning on BADBLK.SYS.
> 
> 
> 
> You say that BADBLK.SYS is used by the file system on HBVS. But when you put a disk into an existing shadowset, BADBLK.SYS just copied over so it's basically useless as a bad block map, right?  I guess it could be useful for the primary volume, the mother of all BADBLK.SYSes in the shadow set.  It can't have any useful info for the any of the media except the one it was originally copied from.  Seem that HBVS has it's own redundancy based approach to dealing with bad blocks.

Anyway if the map in BADBLK.SYS is used on HBVS in some way, that would be interesting.  If I recall correctly, you can't populate BADBLK.sys for the set of shadowed disks.  You can populate it for a individual disk of course, but it had to be removed from the shadowset to do this, and once you put it back into the shadowset it gets copied over.

This is on VMS 7.3-2