Date: Thu, 2 Jun 2005 19:00:09 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: mkb@incubus.de Cc: freebsd-stable@FreeBSD.org, yuval_levy@yahoo.com Subject: Re: filesystems not properly unmounted Message-ID: <200506030200.j53209PW004757@gw.catspoiler.org> In-Reply-To: <429FB785.8030102@incubus.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3 Jun, Matthias Buelow wrote: > Don Lewis wrote: > >> Nope, the ext2fs problem is different. It is caused by ext2fs holding >> persistent references to disk buffers that causes the kernel shutdown >> code to to think that not all the dirty buffers have been written to >> disk and skip unmounting all the file systems. > > Can't that be changed in a way that the kernel checks that in a > per-filesystem granularity instead of seemingly global? I mean, I can > understand that a marginal ext2 fs driver can cause problems with ext2 > filesystems, but affecting other filesystems aswell in such a way is not > nice. That might help to an extent, but would not eliminate the problem. Any file systems between root and the mount point of the ext2 file system would be busy and would not be able to be unmounted. They would still be marked dirty and would need to be fsck'ed after the reboot.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506030200.j53209PW004757>