Xref: utzoo comp.unix.ultrix:2441 comp.sys.dec:2385
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucsd!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.unix.ultrix,comp.sys.dec
Subject: radisk block number reporting
Message-ID: <4544@helios.ee.lbl.gov>
Date: 2 Jan 90 22:28:13 GMT
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: Lbl
Lines: 19
X-Local-Date: 2 Jan 90 14:28:13 PST

Often when doing an radisk to search for bad blocks, the bad block number
reported by the -s (scan) option is off by one (1) from the block number
that the -c (clear error bit) option wants.

In other words, if the scan reports that block 2345 (e.g.) is bad, I have
to say "radisk -c 2344 1 /dev/rrd0c"  to clear the error bit in the
replacement block.

Why the difference?

Disk:       RD53 or RD54 (doesn't seem to matter)
machine:    Vaxstation 2000 or Vaxstation II
controller: RQDX2 (vaxstation II)
Os:         Ultrix 3.0

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.