On Wed, 17 Sep 2003, H. Peter Anvin wrote:
> > Why do you bring the daemon into the picture, it is irrelevant here.
>
> Because it makes it a lot harder to debug the problem.
Ok, fair enough.
The daemon version doesn't matter, any daemon will do. All you need is to
kill -9 automountd while something is mounted, and then unmount everything
by hand without removing the mountpoint directories.
> > # cat /proc/mounts
> > [snip]
> > boxter:(pid29327) /bar autofs rw 0 0
> > boxter:(pid29327) /net autofs rw 0 0
> > boxter:(pid29327) /src autofs rw 0 0
> > boxter:(pid29327) /misc autofs rw 0 0
> > buggy:/n/buggy/misc/homes /misc/homes nfs
> > rw,v3,rsize=8192,wsize=8192,hard,intr,tcp,lock,addr=buggy 0 0
> > # umount /misc/homes
> > # umount /misc
> > # dmesg |tail
> > VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
>
> OK. Did you try Olaf's NFS patch?
This is not an NFS problem. The message occurs regardless of what is
mounted on /misc/homes (NFS, local ext2, bind mount, whatever).
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
