Date: Thu, 23 Jun 2005 12:48:43 +0200 From: Philip Paeps <philip@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: Unable to umount union-parts after umounting unionfs Message-ID: <20050623104843.GA698@loge.nixsys.be> In-Reply-To: <20050623083804.GV738@obiwan.tataz.chchile.org> References: <20050622065357.GA694@loge.nixsys.be> <20050623083804.GV738@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-06-23 10:38:04 (+0200), Jeremie Le Hen <jeremie@le-hen.org> wrote:
> > When playing with union filesystems this morning, I noticed that it's not
> > possible to unmount the directory mounted on union cleanly, even after the
> > union has been cleanly unmounted, once you've read from the union:
> >
> > [...snip...]
> >
> > Strangely, when an 'empty' union is read from, there's no problem
> > unmounting it. It's only when it's read when there's something on it. In
> > other words, from a clean setup:
> >
> > [...snip...]
>
> Could you show us the locked vnodes for these two cases please ?
Unfortunately, 'blank' in both cases. But that might be because I never get
to the debugger 'while' it's unmounting, but always when it has tried and not
succeeded. (I have WITNESS in my kernel, if that matters?).
Is there any way I can either try to unmount the filesystem manually from the
debugger or make the unmounting code more chatting about what it's waiting
for?
I've had a look through the unionfs and unmount code but filesystems look like
a maze of twisty passages in four dimensions without a map or compass nearby.
Good thing this is perfectly reproducible. :-)
- Philip
--
Philip Paeps Please don't Cc me, I am
philip@freebsd.org subscribed to the list.
BOFH Excuse #89:
Electromagnetic energy loss
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050623104843.GA698>