[Top] [All Lists]

Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: 2.6.31 xfs_fs_destroy_inode: cannot reclaim
From: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
Date: Tue, 03 Nov 2009 15:46:05 +0100
Cc: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>, Bas Couwenberg <bas@xxxxxxxxxxxxxxxx>, XFS List <xfs@xxxxxxxxxxx>
In-reply-to: <20091030101601.GA11142@xxxxxxxxxxxxx>
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> <20091030101601.GA11142@xxxxxxxxxxxxx>
User-agent: Thunderbird (Windows/20090812)
Christoph Hellwig wrote:
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.

Sorry for the delay. Yes, XFS_DEBUG was enabled on these servers.

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.

We're back to 2.6.28 at the moment. Please advice if we can do anything to assist.

Any clue why we seem to be the only one hitting this problem? It might have something to do with the short term data retention on these particular servers. All partitions are always 100% full and data is only kept for a couple of days.

Thanks for looking into this.


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