xfs
[Top] [All Lists]

Re: du vs. df inconsistency

To: Jameel Akari <jakari@xxxxxxxxxxx>
Subject: Re: du vs. df inconsistency
From: Stephen Lord <lord@xxxxxxx>
Date: Fri, 04 Feb 2005 10:55:25 -0600
Cc: Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.OSF.4.61.0502041119510.28806@poptart.bithose.com>
References: <Pine.OSF.4.61.0502030956450.28806@poptart.bithose.com> <4202D839.2090003@sgi.com> <Pine.OSF.4.61.0502041043370.28806@poptart.bithose.com> <Pine.OSF.4.61.0502041049300.28806@poptart.bithose.com> <42039EBD.3010001@xfs.org> <Pine.OSF.4.61.0502041119510.28806@poptart.bithose.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (X11/20041127)
Jameel Akari wrote:

Feb 4 10:54:01 alb-ndm kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Feb 4 10:56:32 alb-ndm kernel: XFS: Filesystem sd(8,5) has duplicate UUID - can't mount


The unmount failed beause xfs thought something was still busy, but the
kernel did not. Looks like a reference count leak somewhere in the old
kernel.


That's what I figured. I'll definitely move this to the top of "reasons to upgrade already!" pile. (I'd do it tomorrow if there were some XFS-patched RHEL kernels ready to go... ;)

If you reboot and run repair you should be ok.


I found some mention of this on the mailing list where it was suggested to `mount -o nouuid`. This worked for me - the filesystem recovered itself, and I see the freed space now.


You still have a dangling dead mount inside the kernel, a reboot at an opportune moment will clean that up.

Steve



<Prev in Thread] Current Thread [Next in Thread>