Hi All- We've been having the 'VFS: Busy inodes after unmount' problems like crazy on our desktop and server linux boxes running autofs under 2.4.21 (vanilla). We're using the autofs-3.1.7 userspace tools, but with the autofs4 kernel module.
I applied the patch that was attached earlier in this thread to our kernel and have been running it for the past few days on my desktop. These errors have completely disappeared, and autofs is behaving as expected so far. So, while it might be the wrong thing to do, it does fix our problems. -matt On 18 Sep 2003, Trond Myklebust wrote: > >>>>> " " == Olaf Hering <[EMAIL PROTECTED]> writes: > > > On Wed, Sep 17, H. Peter Anvin 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? > > > I'm not sure, but everyone who has seen this should fiddle this > > patch into the kernel and see how it goes. The whole thing > > started very recently (post 2.4.21) for us. > > > This patch is untested, any feedback appreciated. > > ...and is indeed wrong... It does the exact opposite of what > sillydelete should do. Instead of causing the last application that > closes the file to perform the sillydelete, you are asking the *first* > application that closes it to do so. > Sillydelete *has* to be tied to dentries. Not files, and not > inodes. It is purely a namespace operation... > > So exactly what are you trying to do, and why? > > Cheers, > Trond > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > NFS maillist - [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nfs > _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
