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

[David Laight <david%l8s.co.uk@localhost>]

On Sat, Jan 05, 2008 at 09:39:02AM +0100, Bernd Ernesti wrote:
> > 
> > Unfortunately, fstat shows open files, and if the problem is a
> > refcounting bug on vnodes rather than open files, it is stale vnodes
> > that will be hanging around, and the results of fstat will be null or
> > even misleading.

It could ever be a ref-counting bug on the kernel 'file' structure - although
fstat might be able to report those (even though it won't be able to
locate a process).

> 
> I don't know if this is related, but there were two kernel messages
> before I tried to unmount the filesyste, something which happend during
> the pkgsrc build:
> 
> set{u,g}id pid 7405 (netstat) was invoked by uid 1234 ppid 4328 (shlibsign) 
> with fd 0 closed
> set{u,g}id pid 8477 (netstat) was invoked by uid 1234 ppid 7368 (shlibsign) 
> with fd 0 closed

Not relevant...

        David

-- 
David Laight: david%l8s.co.uk@localhost