Date: Tue, 11 Sep 2007 00:17:42 +0200 From: Johannes Totz <jo_t@gmx.net> To: Peter Schuller <peter.schuller@infidyne.com> Cc: freebsd-fs@freebsd.org, Kris Kennaway <kris@FreeBSD.org> Subject: Re: UFS not handling errors correctly Message-ID: <46E5C286.8010102@gmx.net> In-Reply-To: <20070909200933.GA98161@hyperion.scode.org> References: <46E4225F.1020806@gmx.net> <46E42D14.5060605@FreeBSD.org> <20070909200933.GA98161@hyperion.scode.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Schuller wrote: >> 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? That is want I wanted to report. This corruption should not have happened in the first place. Either some part in geom did not properly report the error back to the upper layer (e.g. the file system); or UFS ignored it silently (as there is nothing in the logs). In any case, the behavior is not correct. But I must also admit that I have no idea what the correct behavior would be like: the write error was most likely a metadata flush (or softupdate checkpoint, not sure of the terminology here) because the (file-)system was idle at that time. Cheers Johannes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46E5C286.8010102>