Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!biivax.dp.beckman.com!rlmeyering
From: rlmeyering@biivax.dp.beckman.com
Newsgroups: comp.sys.dec
Subject: Disk Error recovery info WANTED
Message-ID: <1991Apr3.133352.252@biivax.dp.beckman.com>
Date: 3 Apr 91 20:33:52 GMT
Distribution: comp.os.vms,comp.sys.dec
Organization: Beckman Instruments, Inc.
Lines: 20

Hi everybody !

I am interested in your comments on DEC/EMULEX DISK related error handling from
both a software as well as a hardware perspective.

I have RD53s, RD54s, RA82s, RA92s and EMULEX SD890 and 892s. We often
times receive "SMALL DISK" and "BAD BLOCK REPLACEMENT" errors. I would
like to gain an in depth understanding of the activities that are 
performed by the software and the hardware to determine that a BLOCK is bad
and then to perform the resultant revectoring.

I understand that bad blocks are tracked in different ways for NON-DSA (BADBLK)
vs DSA (Replacement and Caching Table RCT) devices. And that there are two
types of replacement (Host or Controller initiated). However, I would like
more detail...

Any comments are appreciated. Also, any pointers to detailed documentation on
this subject would be helpful.

Thanks NETTERS!