Date: Fri, 6 Aug 2004 14:38:44 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Gary Corcoran <garycor@comcast.net> Cc: DH <dhutch9999@yahoo.com> Subject: Re: Fwd: How to read bad blocks error message & marking of same Message-ID: <20040806193843.GB11465@dan.emsphone.com> In-Reply-To: <4113D950.8000502@comcast.net> References: <20040804181012.71953.qmail@web20423.mail.yahoo.com> <16658.61027.827002.280086@guru.mired.org> <4113D950.8000502@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Aug 06), Gary Corcoran said: > Mike Meyer wrote: > > >Modern drives deal with bad block substitution all by themselves. > > Umm - not quite, right? That is, if a block "goes bad" and you get a > read error, the drive isn't going to do any "substituting" at that > point. You'll just continue to get the read error if you try to > access (read) that block. It's only when you allow another *write* > to that block (e.g. by deleting the original file and writing new > files) that the drive will automatically substitute a spare block for > the one that went bad. SCSI drives, at least, may do automatic reallocation on both reads and writes ( camcontrol mode da0 -m 1, the ARRE and AWRE flags ). If the drive had to reread the block or had to use ECC to recover data, AND the entire block was recovered, it will relocate the data if ARRE is set. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040806193843.GB11465>