Busy inodes after unmount followed by Oops

Busy inodes after unmount followed by Oops

[James Pearson]

There was a long thread a few months ago about this subject:

http://marc.theaimsgroup.com/?t=106332683300004&r=1&w=2

and

http://marc.theaimsgroup.com/?t=106340013500006&r=1&w=2

I've read the posts but as far as I can tell, I can't find a 'solution'
to the problem (but I may have missed it in all the posts!)

I have the same problem with a large number of dual CPU machines running
2.4.20 and above that make heavy use of autofs (v4.0.0pre10).

We get a:

VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice
day...

mesasage, followed some time later by Oops's from kswapd, umount or some
other user application.

Is there a 'fix' for this problem?

Thanks

James Pearson


-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: Busy inodes after unmount followed by Oops

[James Pearson]

James Pearson wrote:
> 
> There was a long thread a few months ago about this subject:
> 
> http://marc.theaimsgroup.com/?t=106332683300004&r=1&w=2
> 
> and
> 
> http://marc.theaimsgroup.com/?t=106340013500006&r=1&w=2
> 
> I've read the posts but as far as I can tell, I can't find a 'solution'
> to the problem (but I may have missed it in all the posts!)
> 
> I have the same problem with a large number of dual CPU machines running
> 2.4.20 and above that make heavy use of autofs (v4.0.0pre10).
> 
> We get a:
> 
> VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice
> day...
> 
> mesasage, followed some time later by Oops's from kswapd, umount or some
> other user application.
> 
> Is there a 'fix' for this problem?

Just to follow up on my original posting back in January, the problem
above appears to have been solved by using Ian Kent's latest autofs
kernel patch (20040508) from
http://www.kernel.org/pub/linux/daemons/autofs/v4 - we are also running
the latest 4.1.2/4.1.3 automount daemon.

We've been running this patch on over 400 machines for the last 10 or so
days, and have not seen any instance of this 'VFS: Busy inodes after
unmount/Oops' problem above - previously, we would have seen a
significant number of these in the same time scale (and we are still
seeing the problem on machines not using the patch).

Thanks

James Pearson

Re: Re: Busy inodes after unmount followed by Oops

[Trond Myklebust]

P=E5 fr , 21/05/2004 klokka 11:44, skreiv James Pearson:

> We've been running this patch on over 400 machines for the last 10 or so
> days, and have not seen any instance of this 'VFS: Busy inodes after
> unmount/Oops' problem above - previously, we would have seen a
> significant number of these in the same time scale (and we are still
> seeing the problem on machines not using the patch).

Note  that Greg's patch for solving the NFS client issues that were
revealed by this bug is in 2.4.26 (and in 2.6.5)...

Cheers,
  Trond


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs