Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Umount a filesystem fails, even if no proccesses are accessing it




To: current-users%NetBSD.org@localhost

Subject: Re: Umount a filesystem fails, even if no proccesses are accessing it

From: Bernd Ernesti <netbsd%lists.veego.de@localhost>

Date: Fri, 4 Jan 2008 22:58:54 +0100


On Fri, Jan 04, 2008 at 01:44:47PM -0800, Aaron J. Grier wrote:
> On Mon, Dec 24, 2007 at 11:33:36PM +0100, Bernd Ernesti wrote:
> > I'm in the situation where I try to unmount a filesystem which has the
> > NetBSD sources on it, but I just get a
> >  umount: /home/source: Device busy

[..]

> there are still handles open on /home/source.  "fstat -f /home/source"
> may reveal which processes which have them open.

I used fstat, but I can't remeber now if I used it with -f, where that flag
shouldn't make a difference since -f only narrows down the search to one
file system.

fstat didn't show any open file handles for /home/source

Bernd




Follow-Ups:

Re: Umount a filesystem fails, even if no proccesses are accessing it
From: David Holland


References:

Re: Umount a filesystem fails, even if no proccesses are accessing it
From: Aaron J. Grier




Prev by Date: Re: Umount a filesystem fails, even if no proccesses are accessing it

Next by Date: Re: INSTALL_LARGE build failure

Previous by Thread: Re: Umount a filesystem fails, even if no proccesses are accessing it

Next by Thread: Re: Umount a filesystem fails, even if no proccesses are accessing it

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index