Skip to contentSkip to conversation

umount() and NFS races in 2.4.26

DISCUSSION James Pearson 1 participant 1 message Jul 9, 2004

lore
Share & tools
lore
#0 lore raw

Thomas Moestl:

Quoted 7 lines

after deploying an SMP machine at work, we started to experience Oopses
in file-system related code relatively frequently. Investigation
revealed that they were caused by references using junk pointers from
freed super blocks via dangling inodes from unmounted file systems;
Oopses would always be preceded by the warning
VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... on an unmount (unmount activity is high on this machine due to heavy >use of the automounter).

Are you using the latest autofs4 kernel patches?

I had a similar problem - see the thread at:

http://marc.theaimsgroup.com/?l=linux-nfs&m=108515468003933&w=2

The latest autofs4 patches fixed it for me - available from:

http://www.kernel.org/pub/linux/daemons/autofs/v4

James Pearson