Date: Fri, 12 Apr 2002 09:21:45 +0300 From: Valentin Nechayev <netch@iv.nn.kiev.ua> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: Coleman Kane <cokane@FreeBSD.ORG>, David Schultz <dschultz@uclink.Berkeley.EDU>, Bob Bishop <rb@gid.co.uk>, stable@FreeBSD.ORG Subject: Re: very old bug Message-ID: <20020412092145.A227@iv.nn.kiev.ua> In-Reply-To: <200204111604.aa64453@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Thu, Apr 11, 2002 at 04:04:42PM %2B0100 References: <20020411100223.A64698@freebsd.org> <200204111604.aa64453@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
Thu, Apr 11, 2002 at 16:04:42, iedowse (Ian Dowse) wrote about "Re: very old bug": > If an error occurs when the write is finally attempted, the buffer > cache is left in a predicament because it has no way to inform the > filesystem of the problem, and it can't just throw away the data > without risking serious filesystem corruption, and confusion within > the filesystem code. The two remaining options are to keep retrying > the write in the hope that it will eventually succeed, or panic. > > About the only other safe thing to do would be to completely > disassociate the failing device from the filesystem and throw away > any unwritten data. If the filesystem can handle the device going > away like this without panicking, then maybe the user might be able > to unmount it and contunue. Consider not floppy, but HDD, particularly one where root FS is placed.:( Panic or dissociation won't be good solution. Forever loop to write is somehow best, but it should give big delays for other processes work. But if FS carrier disappears, FS must be disassociated. But this is only pink dreams... /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020412092145.A227>