xfs
[Top] [All Lists]

Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim

To: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
Subject: Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 30 Oct 2009 06:16:01 -0400
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>, Bas Couwenberg <bas@xxxxxxxxxxxxxxxx>, XFS List <xfs@xxxxxxxxxxx>
In-reply-to: <89c4f90c0910280519k759230c1r7b1586932ac792f7@xxxxxxxxxxxxxx>
References: <20091007011926.GB32032@xxxxxxxxxxxxx> <4AD18C8D.90808@xxxxxxxxxxxxxxxx> <20091012233854.GA29446@xxxxxxxxxxxxx> <20091019011600.GO9464@xxxxxxxxxxxxxxxx> <20091019035426.GB18296@xxxxxxxxxxxxx> <20091020034048.GA9464@xxxxxxxxxxxxxxxx> <89c4f90c0910210245h4691cd82hd1d63f5ed72fb2e3@xxxxxxxxxxxxxx> <20091022085937.GA2039@xxxxxxxxxxxxx> <89c4f90c0910270341r7833f490g60810f2817eb0950@xxxxxxxxxxxxxx> <89c4f90c0910280519k759230c1r7b1586932ac792f7@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Oct 28, 2009 at 01:19:44PM +0100, Tommy van Leeuwen wrote:
> Another one just seconds ago. Might be more usefull then the last 2.

Ist this one also with COFNIG_XFS_DEBUG enabled?  May assert should have
hit the condition we're seing in that one earlier.

Anyway, it still looks like we can get inodes that are partially
or fully torn down before entering ->destroy_inode.  I'll try to figure
out why.

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