Date: Tue, 26 Oct 2004 13:25:33 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: freebsd-fs@merdin.com Cc: freebsd-fs@FreeBSD.org Subject: Re: Re[2]: panic again Message-ID: <200410262025.i9QKPXeV018690@gw.catspoiler.org> In-Reply-To: <1357841854.20041026213409@merdin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26 Oct, Pavel Merdine wrote: > Again, somehow after a panic on ONE file system, other filesystems are > not fully synced. The system conplaints that they are dirty after > restart. So it seems like one panic lead to corruption of another > systems. Maybe I'm wrong here too. But I dont see any good in fsck-ing > each time. When the OS detects these types of problems, then something (we don't know what) unexpected has happened, so we can no longer trust the state of the machine. If we can't trust the state of the machine, then it is dangerous to sync any of the file systems, because doing so could damage them with corrupt data. > Background fsck does not work in reality as well, because the system > can panic thousand times before errors are fixed. It might be a good idea to force a foreground fsck if the system panics before a background fsck has marked a dirty filesystem clean.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410262025.i9QKPXeV018690>