[Top] [All Lists]

Re: 2.6.30 panic - xfs_fs_destroy_inode

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: 2.6.30 panic - xfs_fs_destroy_inode
From: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
Date: Mon, 20 Jul 2009 21:19:43 +0200
Cc: linux-xfs@xxxxxxxxxxx, Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>, Lachlan McIlroy <lmcilroy@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>
In-reply-to: <20090630204256.GA1891@xxxxxxxxxxxxx>
Organization: News-Service.com
References: <4A408316.2070903@xxxxxxxxxxxxxxxx> <1587994907.388291245745033392.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090623171305.GB23971@xxxxxxxxxxxxx> <4A4A7205.6010101@xxxxxxxxxxxxxxxx> <20090630204256.GA1891@xxxxxxxxxxxxx>
User-agent: Thunderbird (Windows/20090605)
Hi Christoph,

I saw some patches from your hand on this list ("fixes for memory allocator recursions into the filesystem"). Are these patches related to this issue?



Christoph Hellwig wrote:
On Tue, Jun 30, 2009 at 10:13:57PM +0200, Patrick Schreurs wrote:
Hi (again),

Anyone has any advice to prevent this from happening? We've seen 10 crashes in the last 14 days. Would it be helpful to enable CONFIG_XFS_DEBUG? Does this result in a big performance hit on busy xfs filesystems? If we can help troubleshoot this problem, please advice.

If i understand correctly this issue also exists in 2.6.29? Should i downgrade to the latest 2.6.28 kernel to regain stability?

For now please downgrade to the latest 2.6.28, yes.  I hope I will have
time and machine ressources to dig deeper into the problem this week.

xfs mailing list

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