Date: Tue, 6 Jun 2000 08:35:24 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Neil Blakey-Milner <nbm@mithrandr.moria.org> Cc: Oleg Derevenetz <oleg@oleg.vsi.ru>, freebsd-hackers@FreeBSD.ORG Subject: Re: Write-protected floppy crash Message-ID: <200006061535.IAA94049@apollo.backplane.com> References: <Pine.BSF.4.21.0006061906450.8772-100000@oleg.vsi.ru> <20000606172431.A15405@mithrandr.moria.org>
index | next in thread | previous in thread | raw e-mail
:On Tue 2000-06-06 (19:13), Oleg Derevenetz wrote:
:> When write-protected floppy mounted in R/W mode, write attempt to this
:> floppy follows kernel panic (dirty buffers) and reboot. Is this correct ?
:> The best way IMO is to always mount write-protected floppies in R/O mode.
:
:It's not 'correct', but it does happen, and is copiously documented and
:mentioned on various mailing lists. It would be nice if you could fix
:it *grin*.
:
:Neil
:--
:Neil Blakey-Milner
The behavior is probably outfall from buffer cache changes for 4.0,
but it would have to be fixed a different way. The buffer cache
changes were basically to not throw away dirty buffers with write errors
because doing so could result in extremely serious filesystem
corruption due to the system making modifications to meta data (the
dirty buffer) and then having them magically, randomly 'revert' out
from under it due to the write error. Result: catastrophic filesystem
corruption.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006061535.IAA94049>