xfs
[Top] [All Lists]

Re: Busy inodes after umount

To: Ragnar Kjørstad <xfs@xxxxxxxxxxxxxxxxxxx>
Subject: Re: Busy inodes after umount
From: Matthew Jacob <mjacob@xxxxxxxxx>
Date: Thu, 19 Jul 2001 16:58:36 -0700 (PDT)
Cc: "Christian, Chip" <chip.christian@xxxxxxxxxxxxxxx>, <linux-xfs@xxxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20010720015343.B11236@xxxxxxxxxxx>
Reply-to: <mjacob@xxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
I reported this a couple of months back. It's reassuring to know that it's a
consistent problem.

On Fri, 20 Jul 2001, [iso-8859-1] Ragnar Kjørstad wrote:

> On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote:
> > I found the same thing happening.  Tracked it down in our case to using 
> > fdisk to re-read disk size before mounting.  Replaced it with "blockdev 
> > --readpt" and the problem seems to have gone away.  YMMV.
>
> I've now been able to reproduce:
>
> * make a filesystem
> * mount it
> * export it (nfs)
> * mount on remote machine
> * lock file (fcntl)
> * unexport
> * unmount
>
> Then you get the VFS message about self-destruct. Tested with both ext2
> and xfs.
>
> The lock is still present in /proc/locks after the umount.
>
> With ext2 I can remount the filesystem successfully, but with XFS I get
> the message about duplicate UUIDs and the mount failes. I believe this is a 
> totally
> different problem from the one you were experiencing. (and blockdev doesn't 
> help for me)
>
> I suppose this is a generic kernel bug?
>
>
>


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