[Info-vax] analyze/disk errors

[tadamsmar]

On Thursday, December 5, 2013 3:04:50 PM UTC-5, Stephen Hoffman wrote:
> On 2013-12-05 19:32:07 +0000, tadamsmar said:
> 
> 
> 
> > That's not what the VMS documentation says.  This thread is interesting 
> 
> > in that I have never once got advice here that just flat out 
> 
> > contradicts the documentation and yet it keeps happening in this 
> 
> > thread.  Also I did what the documentation said to do and nothing 
> 
> > happened that contradicted the documentation.
> 
> 
> 
> Either the documentation is wrong, or it's being misread.
> 
> 
> 
> >> Ask your friend backup to restore the "some other files".
> 
> > 
> 
> > Not sure what you mean. I restored all the files on the disk.
> 
> 
> 
> At US$30 a pop for decent 146 GB 10K SCSI disks (new), messing around 
> 
> with old disks that are tossing errors isn't worth the time.

Where can you find a new one for $30?

Even if it's $60, you have a point.  I think these anal/disk problems arose when I was switching the drive around (from a DS10 to an AS800 to another DS10).  Now it's back in a replacement system where it should stay till that system fails.

It "logged" anal/disk warnings at some point, but I don't think it logged errors during all this, but maybe I overlooked something.

I suppose I could exercise the media and all that.

I am using anal/disk more these days, so I can better pin-point when something goes wrong.

> 
> 
> 
> > Here's what I get on the system in question:
> 
> > 
> 
> > $  copy dsa0:[000000]badblk.sys nla0:
> 
> > %COPY-E-READERR, error reading DSA0:[000000]BADBLK.SYS;1
> 
> > -RMS-F-RER, file read error
> 
> > -SYSTEM-F-ILLBLKNUM, illegal logical block number
> 
> > %COPY-W-NOTCMPLT, DSA0:[000000]BADBLK.SYS;1 not completely copied
> 
> 
> 
> Probably off the end of the disk.   It's a file you should not 
> 
> generally be directly accessing.  The file system and tools 
> 
> special-cases it, though it would appear ANALYZE /DISK isn't doing a 
> 
> stellar job of accessing it.
> 
> 
> 
> 
> 
> > Not sure what role badblk.sys has in a shadowset if any, but it's 
> 
> > certainly not the same role is plays on a non-shadow set disk.
> 
> 
> 
> It's where inaccessable blocks live.  End of the disk blocks.  
> 
> Sometimes reserved blocks.   With HBVS, bad blocks transiently.
> 
> 
> 
> 
> 
> -- 
> 
> Pure Personal Opinion | HoffmanLabs LLC