On Tue, Nov 21, 2000 at 07:19:21PM -0800, Brian Pomerantz wrote:
> On Wed, Nov 22, 2000 at 02:17:37PM +1100, David Gibson wrote:
> > In testing/fixing ramfs I've discovered a bug where umount() fails
> > with -EBUSY for no readily apparent reason. I haven't yet found any
> > way to unmount the fs once it gets into this state. I'm also not sure
> > what triggers the problem.
> >
> > I thought this was a ramfs bug, but I've now seen a similar problem
> > with an ext fs on a loop device (while running the LSB/Posix
> > testsuite).
> >
> > Has anyone else encountered this problem?
> >
>
> You're sure there aren't any programs that have the mounted file
> system as a current working directory? (I know this is a stupid
> question, but that's is the only time I've seen this)
I don't think so: there's certainly nothing running that ought to have
its cwd there, and 'fuser -m' doesn't show anything.
--
David Gibson, Technical Support Engineer, Linuxcare, Inc.
+61 2 6262 8990
[EMAIL PROTECTED], http://www.linuxcare.com/
Linuxcare. Support for the revolution.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to [EMAIL PROTECTED]
