On Wed, 13 Nov 2002 18:22:04 -0600
Tom Wike <[EMAIL PROTECTED]> wrote:
> Hi,
> We are seeing allot of messages like this (from /var/log/messages)
> on our Linux compute servers (IBM x330 & X335 boxes):
> Nov 13 14:49:21 lnx0129 automount[948]: attempting to mount entry
> /data/lsf Nov 13 14:50:36 lnx0129 automount[948]: attempting to
> mount entry /data/alpha1 Nov 13 14:54:52 lnx0129 kernel: VFS: Busy
> inodes after unmount. Self-destruct in 5+seconds. Have a nice
> day... Nov 13 14:54:52 lnx0129 automount[27090]: expired /data/lsf
> Nov 13 14:59:52 lnx0129 automount[27092]: expired /data/alpha1
>
> I was wondering if anyone has ever seen this before? We are using
> the RedHat7.2 2.4.9-31Enterprise kernel, we are forced to stay with
> this version of kernel because of Clearcase v4.2 support is needed.
> I found this blurb from the linux-kernel mailing list:
>
> * From: Tad Dolphay
> * Subject: Re: Busy inodes after umount
> * Date: Thu, 19 Jul 2001 17:15:38 -0700
> I know there was a fix for a "Busy inodes after unmount" problem in
> 2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list
> from Neil Brown:
>
> -------------Included message-----------------------
> Previously anonymous dentries were hashed (though with no name,
> the hash was pretty meaningless). This meant that they would hang
> around after the last reference was dropped. This was actually
> fairly pointless as they would never get referenced again, and
> caused a real problem as umount wouldn't discard them and so you
> got the message
> printk("VFS: Busy inodes after unmount. "
> "Self-destruct in 5 seconds. Have a nice
> day...\n");
>
> In 2.4.6-pre3 I stopped hashing those dentries so now when the
> last reference is dropped, the dentry is freed. So now there will
> never be more anonymous dentries than there are active nfsd
> threads.
> ---------------end included message-------------------
>
> So it appears to have been fixed? Anyways please let me know if you
> have any comments or questions in regards to this matter. Thanks!
>
>
I haven't a clue, but did find this on a Google search ("busy
innodes after unmount" +clearcase).
Mind the linewrap:
http://www.rational.com/techsupport/clearcase/tech/patchlink/new/clearcase/4.1j/clearcase_p4.1j-10/clearcase_p4.1j-10.sun5.readme
There is mention of a "bugfix" for Clearcase in the above .readme:
---snip-->
Bug CMBU00052877 Description
%severity Sv2
%bug_desc_begin
Corrects a defect that could cause the MVFS to hang after a cleartool
umount
command. Kernel error messages associated with this hang include the
text
"VFS: Busy inodes after unmount."
%bug_desc_end
---snip-->
Best,
Tom
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
