Date: Sun, 9 Sep 2007 22:09:34 +0200 From: Peter Schuller <peter.schuller@infidyne.com> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-fs@freebsd.org, Johannes Totz <jo_t@gmx.net> Subject: Re: UFS not handling errors correctly Message-ID: <20070909200933.GA98161@hyperion.scode.org> In-Reply-To: <46E42D14.5060605@FreeBSD.org> References: <46E4225F.1020806@gmx.net> <46E42D14.5060605@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] > bg fsck cannot fix arbitrary filesystem corruption. Nor is it intended to. But is not the proposed problem that UFS caused the corruption to begin with? Given that updates are already done in such a way as to cause predictable inconsistency in the event of a crash, should not appropriate course of action in a case such as this be to panic, unmount the fs, rollback and error out, or otherwise abort the operation in a way the filesystem can be fsck:ed and re-mounted (assuming the device is alive), rather than cause corruption? -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG5FL9DNor2+l1i30RAj49AJ0beAgk+Vua8EHZvXM2OIFu3tOkcACfW+4i VBTspk6BIGd6DU6Jt9xeohs= =DZqC -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070909200933.GA98161>