[4426] in linux-scsi channel archive
Re: Bad blocks: How many?
daemon@ATHENA.MIT.EDU (Dr. Michael Weller)
Tue Jul 21 14:01:28 1998
Date: Tue, 21 Jul 1998 19:09:12 +0200 (MESZ)
From: "Dr. Michael Weller" <eowmob@exp-math.uni-essen.de>
To: Jon Lewis <jlewis@inorganic5.fdt.net>
Cc: Tim Robinson <timr@sykes.demon.co.uk>, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.95.980721104703.1253f-100000@tarkin.fdt.net>
On Tue, 21 Jul 1998, Jon Lewis wrote:
> On Tue, 21 Jul 1998, Dr. Michael Weller wrote:
>
> > Well, at first there are 0 grown defects, so what. Of course, you should
> > check the AWRE and ARRE settings and the amount of spare sectors to use in
> > case of defects. If the disk cannot reallocate bad sectors due to wrong
> > settings there, they won't show up as defects. (actually I'm not 100% sure
> > if such on the fly defects are added to the grwon list or if you have to
> > run a format and disk certify process to add to the grown list).
>
> Does anyone know if the grown list is really read properly? I don't think
Well, as the guy who made the last patches to scsiinfo I must admit I
never witnessed it reporting more than 0 grown defects either (on my
disks). The code is, however, virtually 100% equal to the manufacturer's
defects with only 1 or 2 bits in the query command different. I'm pretty
sure it is ok.
Like I said, I'm not sure if on the fly reallocated sectors are added to
the grown defects. It might be that (at least on some disks) the grown
table is only filled with defects occuring during a format operation.
Honestly, the SCSI standard gives the manufacturers much freedom here.
> I've ever seen scsi-config report anything in the grown list. Just
> recently, I was setting up some Micropolis 1991's and 3 were "bad". 1
> could not be formatted without lots of errors locking up the system. 2
> were formattable but generated unrecoverable read errors when tested. I
---------------------------------------
Uhmm.. Did you actually enable disk certify (verifying) with the format
command? Well, I think it is default anyhow. Nevertheless it is up to the
disk to actually perform such verifies. I'm just surprised it produces
read errors right after format. It should already have found those defects
during the format. This does not really shed a good light on the firmware.
Michael.
--
Michael Weller: eowmob@exp-math.uni-essen.de, eowmob@ms.exp-math.uni-essen.de,
or even mat42b@spi.power.uni-essen.de. If you encounter an eowmob account on
any machine in the net, it's very likely it's me.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
