On Wed, 17 Sep 2003 13:41:15 -0700, H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Okay... let me ask this so I get it straight...
>
> Has anyone seen this (busy inodes after stopping the automounter) using
> autofs v3 kernel module and daemon?
Why do you bring the daemon into the picture, it is irrelevant here.
Sure it probably does things differently which might avoid the error,
but the kernel issue exists nonetheless.
To answer your question again: yes, the issue is present in both v3 and
v4 kernel modules. You can always replicate it yourself if you don't
believe me, using the little recipe I posted earlier:
# lsmod | grep autofs
autofs 11236 4 (autoclean)
# 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...
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
