Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 04 Feb 2005 08:55:31 -0800 (PST) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.131.35]) by oss.sgi.com (8.13.0/8.13.0) with ESMTP id j14GtTfL024170 for ; Fri, 4 Feb 2005 08:55:29 -0800 Received: from filter02.roc.ny.frontiernet.net (filter02.roc.ny.frontiernet.net [66.133.131.177]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id D821410299; Fri, 4 Feb 2005 16:55:28 +0000 (UTC) Received: from relay02.roc.ny.frontiernet.net ([66.133.131.35]) by filter02.roc.ny.frontiernet.net (filter02.roc.ny.frontiernet.net [66.133.131.177]) (amavisd-new, port 10024) with LMTP id 28518-34-37; Fri, 4 Feb 2005 16:55:28 +0000 (UTC) Received: from [192.168.1.65] (67-137-96-87.dsl2.brv.mn.frontiernet.net [67.137.96.87]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id 8A4AC1020C; Fri, 4 Feb 2005 16:55:23 +0000 (UTC) Message-ID: <4203A8FD.2040002@xfs.org> Date: Fri, 04 Feb 2005 10:55:25 -0600 From: Stephen Lord User-Agent: Mozilla Thunderbird 0.9 (X11/20041127) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jameel Akari Cc: Eric Sandeen , linux-xfs@oss.sgi.com Subject: Re: du vs. df inconsistency References: <4202D839.2090003@sgi.com> <42039EBD.3010001@xfs.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on oss.sgi.com X-Virus-Scanned: by amavisd-new-20040701 (2.0) at filter02.roc.ny.frontiernet.net X-Virus-Status: Clean X-archive-position: 4881 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@xfs.org Precedence: bulk X-list: linux-xfs 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