On Mon, 29 Sep 2003, Ion Badulescu wrote:
> 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.
>
Yes, your'e exactly right. That's expected behaviour as the directory
dentries still exist and there is no daemon to remove them. Hence the
message. Seeing this message has always been a signal to me that the
daemon has a bug.
I have been thinking that implementing a umount_begin routine in the
super_operations for autofs4 would remedy the problem. I believe that,
correct me if I'm wrong, the umount must be done with a force option in
this case, so the umount_begin would be called.
snip ...
> >
> > 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).
I must admit, reading through the thread, I was wondering how it could
be an NFS problem.
--
,-._|\ Ian Kent
/ \ Perth, Western Australia
*_.--._/ E-mail: [EMAIL PROTECTED]
v Web: http://themaw.net/
_______________________________________________
autofs mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/autofs
