* VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
@ 2006-12-28 9:27 Jesper Juhl
2006-12-28 9:43 ` Jan Engelhardt
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Jesper Juhl @ 2006-12-28 9:27 UTC (permalink / raw)
To: linux-kernel; +Cc: Trond Myklebust, nfs, jesper.juhl
I get this message in my webservers (with NFS mounted homedirs) logs once
in a while :
kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
It doesn't seem to have any bad effect on anything, but it would be nice
to know if there is any cause for concern.
The NFS server is running 2.6.18.1 and the webservers are running 2.6.17.8
--
Jesper Juhl <jesper.juhl@gmail.com>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
2006-12-28 9:27 VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day Jesper Juhl
@ 2006-12-28 9:43 ` Jan Engelhardt
2006-12-28 10:32 ` Ian Kent
2006-12-28 13:02 ` [NFS] " Jeff Layton
2 siblings, 0 replies; 4+ messages in thread
From: Jan Engelhardt @ 2006-12-28 9:43 UTC (permalink / raw)
To: Jesper Juhl; +Cc: linux-kernel, Trond Myklebust, nfs
On Dec 28 2006 10:27, Jesper Juhl wrote:
>
>I get this message in my webservers (with NFS mounted homedirs) logs once
>in a while :
>
> kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
This happens when the underlying "block device" disappears, the most
prominent case being ejecting the CD while the fs is still mounted. I
have not seen it with nfs yet, since networked fs don't have any
real backing device and instead provide either [waiting for
reconnection] or -EIO, i.e. proper error handling.
>
-`J'
--
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
2006-12-28 9:27 VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day Jesper Juhl
2006-12-28 9:43 ` Jan Engelhardt
@ 2006-12-28 10:32 ` Ian Kent
2006-12-28 13:02 ` [NFS] " Jeff Layton
2 siblings, 0 replies; 4+ messages in thread
From: Ian Kent @ 2006-12-28 10:32 UTC (permalink / raw)
To: Jesper Juhl; +Cc: linux-kernel, Trond Myklebust, nfs
On Thu, 28 Dec 2006, Jesper Juhl wrote:
>
> I get this message in my webservers (with NFS mounted homedirs) logs once
> in a while :
>
> kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
>
> It doesn't seem to have any bad effect on anything, but it would be nice
> to know if there is any cause for concern.
It's at least a memory leak.
>
> The NFS server is running 2.6.18.1 and the webservers are running 2.6.17.8
Strange, I've not heard of this message appearing for a long time now.
Ian
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [NFS] VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
2006-12-28 9:27 VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day Jesper Juhl
2006-12-28 9:43 ` Jan Engelhardt
2006-12-28 10:32 ` Ian Kent
@ 2006-12-28 13:02 ` Jeff Layton
2 siblings, 0 replies; 4+ messages in thread
From: Jeff Layton @ 2006-12-28 13:02 UTC (permalink / raw)
To: Jesper Juhl; +Cc: linux-kernel, nfs, Trond Myklebust
Jesper Juhl wrote:
> I get this message in my webservers (with NFS mounted homedirs) logs once
> in a while :
>
> kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
>
> It doesn't seem to have any bad effect on anything, but it would be nice
> to know if there is any cause for concern.
>
It is cause for concern. This means that the filesystem was unmounted (and the
superblock was freed), but the inode structs are still hanging around. The
"self-destruct" is telling you that eventually, this machine will crash due to
this. If you see this message you should probably plan a reboot sometime.
What will happen is that eventually the kernel may try to reference these
inodes, but they now have pointers into a freed superblock. If that superblock
memory was reused for another purpose, you'll likely crash.
IMO, we should probably consider this to be a BUG(), but that only really is
helpful if you can capture a coredump and can try to track down why these inodes
couldn't be flushed correctly. In the very least, it's probably time to change
this message to be less cryptic.
I've seen some sporadic reports of this problem on earlier kernels in situations
where a NFS server is unable to be contacted for a while, but have not gotten
enough info to get a handle on it.
-- Jeff
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-12-28 13:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-12-28 9:27 VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day Jesper Juhl
2006-12-28 9:43 ` Jan Engelhardt
2006-12-28 10:32 ` Ian Kent
2006-12-28 13:02 ` [NFS] " Jeff Layton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox