Date: Thu, 2 Jun 2005 16:53:46 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: cswiger@mac.com Cc: freebsd-stable@FreeBSD.org, yuval_levy@yahoo.com Subject: Re: filesystems not properly unmounted Message-ID: <200506022353.j52NrkEH004579@gw.catspoiler.org> In-Reply-To: <363CBD31-8CA6-41F7-99D2-E11BC5D84FC2@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Jun, Charles Swiger wrote: > On Jun 2, 2005, at 4:56 PM, yuval levy wrote: >>> If it's a pain to remeber, maybe try sticking >>> something in rc.shutdown? >> >> Thank you for trying to help, but I do not find this >> reply helpful. That's a quick and dirty fix, not a >> solution. > [ ...car analogy snipped... ] >> Quick and dirty fixes are ok for the short term, but >> this issue has been around for too long. I wish I had >> the knowledge to fix it... > > There's a discussion on -current called "Re: [RFC] [PATCH] VM & VFS > changes" which may help resolve the issue of unmounting and flushing > the tree of filesystems more cleanly, which you should look into and > be willing to test as code comes out. 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506022353.j52NrkEH004579>