Date: Thu, 29 Mar 2007 23:40:49 +0200 From: Ivan Voras <ivoras@fer.hr> To: freebsd-fs@freebsd.org Subject: Re: gvirstor & UFS Message-ID: <euhbp2$9lh$1@sea.gmane.org> In-Reply-To: <20070330062726.I2388@besplex.bde.org> References: <euca4b$6l8$1@sea.gmane.org> <20070328100536.S6916@besplex.bde.org> <euh5hh$iis$1@sea.gmane.org> <20070330062726.I2388@besplex.bde.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Bruce Evans wrote: > That is hard to fix. The change to vfs_bio.c to not discard buffer > contents > after a write error (rev.1.196 of vfs_bio.c) may even have been triggered > by this and similar panics in soft updates. However, I think it is a bug > for file systems to not be able to deal with i/o errors. Rev.1.196 could > have reasonably left the buffer alone instead of discarding it as before > or clearing its error indicator and dirty flag as now, so that file system > code could deal with the error a little later. Then I think the above > panic would still occur, sincs soft updates can't deal with the error. > Soft updates is apparently depending on not even seeing the error. But > some errors are non-recoverable, so not seeing them is no solution. Ah. It looks like I've again stumbled on a task that needs non-trivial interaction with the UFS (the last time was gjournal, which Pawel thankfully took over and made it work) :( I can probably try solving this one, but I'll need major hand-holding through it since I'm afraid of the UFS code. Any volunteers? [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGDDJhldnAQVacBcgRAqxlAJ429DbUz2zidKwmetc3FJ1dhbdVOgCgqWSO QQMZ4GUyyDN8XhswMcg23OY= =bpsz -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?euhbp2$9lh$1>