Date: Wed, 29 Aug 2007 12:27:57 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Max Laier <max@love2party.net> Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, Pascal Hofstee <caelian@gmail.com> Subject: Re: ZFS kernel panic Message-ID: <86absa3aaa.fsf@ds4.des.no> In-Reply-To: <200708282324.05834.max@love2party.net> (Max Laier's message of "Tue\, 28 Aug 2007 23\:23\:56 %2B0200") References: <20070828211440.470805B3B@mail.bitblocks.com> <200708282324.05834.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Max Laier <max@love2party.net> writes: > This is complete nonsense! As you pointed out earlier zfs doesn't > know anything about the nature of the error. There is only one > sensible way to deal with a disk error - unless it is transient - and > that is stopping all (write) access to the drive. As you can't easily > move a mounted drive with opened files into read-only mode, a panic is > the only way to make sure. Actually, remounting the disk read-only upon encountering a write error is standard behaviour in Linux. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86absa3aaa.fsf>