Date: Tue, 21 Nov 1995 19:43:30 -0800 (PST) From: Julian Elischer <julian@ref.tfs.com> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hasty@rah.star-gate.com, hackers@FreeBSD.org Subject: Re: Help! I got a bad block.... Message-ID: <199511220343.TAA07906@ref.tfs.com> In-Reply-To: <199511220326.DAA24614@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 22, 95 03:26:01 am
next in thread | previous in thread | raw e-mail | index | archive | help
the drive will not forward the block if it thinks it can't recover the data that's why a write of nulls to the block SHOULD succeed.. it can forward that , knowing that the previous contents no-longer matter.. There is code in the driver to order a single block to be forwarded.. It's all there.. all it needs is to call the appropriate function from an ioctl. The only thing that was holding me back was the question of which .h file should define the ioctl..? > > Julian Elischer stands accused of saying: > > > > No in fsck it attempts to write nulls to the inode > > which requires it to read the block first, > > null out the inode, and write it back..... > > the read is failing.. > > With ARRE enabled, the block should be forwarded on read as well. If it's > not, I'm not sure where you'd stand. (Is there a "forwarded block, may be > corrupt" case with SCSI drives that might be causing the read command to > still fail, even though the block has been relocated? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511220343.TAA07906>