xfs
[Top] [All Lists]

Re: 2.6.30 panic - xfs_fs_destroy_inode

To: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
Subject: Re: 2.6.30 panic - xfs_fs_destroy_inode
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 17 Aug 2009 17:14:37 -0400
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, Lachlan McIlroy <lmcilroy@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>
In-reply-to: <89c4f90c0907220155u5d9331dj3cbe53efcf6b51f2@xxxxxxxxxxxxxx>
References: <4A408316.2070903@xxxxxxxxxxxxxxxx> <1587994907.388291245745033392.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090623171305.GB23971@xxxxxxxxxxxxx> <4A4A7205.6010101@xxxxxxxxxxxxxxxx> <20090701124441.GA12844@xxxxxxxxxxxxx> <4A4CEEF2.7040101@xxxxxxxxxxxxxxxx> <20090721141225.GA24330@xxxxxxxxxxxxx> <89c4f90c0907220155u5d9331dj3cbe53efcf6b51f2@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Jul 22, 2009 at 10:55:54AM +0200, Tommy van Leeuwen wrote:
> Unfortunately we still get errors, with this patch on top of the
> previous one: The difference is that is now crashes within an hour
> instead of once a week, so that might be good for troubleshooting.

Hi Tommy and sorry for dropping the ball on this, I didn't remember this
mail anymore until I look for more reporters of the inode related
problems.

Current mainline (Linus' git as of today) has a lot of the fixes in this
area, any chance I could trick you into trying it?  Maybe including the
debug patch below which adds a printk to that one culprit that I thing
might remain:

Also if it still happens any chance you could send output of the dmesg
command instead of the syslog files?  For some reason syslogd usually
eats up some bits of kernel oops message..


Index: linux-2.6/fs/xfs/xfs_iget.c
===================================================================
--- linux-2.6.orig/fs/xfs/xfs_iget.c    2009-08-17 18:08:39.563217129 -0300
+++ linux-2.6/fs/xfs/xfs_iget.c 2009-08-17 18:09:12.999316531 -0300
@@ -242,6 +242,8 @@ xfs_iget_cache_hit(
 
                error = -inode_init_always(mp->m_super, inode);
                if (error) {
+                       printk("XFS: inode_init_always failed to re-initialize 
inode\n");
+
                        /*
                         * Re-initializing the inode failed, and we are in deep
                         * trouble.  Try to re-add it to the reclaim list.

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