xfs
[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: Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Aug 2009 14:24:59 +0200
Cc: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, Lachlan McIlroy <lmcilroy@xxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=rwkgNlkHv/w9Mz1nc7gdWGmEvfCXtZrjJ1gY7FZOYTw=; b=hjpbwA9KP9PWbS8jL955O50IxwtF+3SQAC/K6/vb4h0zBfcgOYkB0lhBnhxcdF9s9B sGi+StmrXDoHQqIZ7c16fuZNBwL1deL15KuepkFfXmV9fXn8C5izv6qiZFywycp+HKm+ /SMqFcYi7ijc08GRX2bkZkZqEGLkEHatAVTso=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=BVnZvGtAsl/DThZfsfhrAwizCmFQONfgatt8B4NrabHQUQvNUXt7EDPAx7Fc/bxA4A MuWTL9Rr8sCMR2BloSlFPEmGCDobXNBQgRDIHDLQ3bk8SEw/Kv5mw2IVd5fm4QNRaXSI WIrC0yu6G9h2lK6SjsXeu3hL2TsbdoNCtk1Tw=
In-reply-to: <20090817211437.GA5929@xxxxxxxxxxxxx>
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> <20090817211437.GA5929@xxxxxxxxxxxxx>
Sender: chiparus@xxxxxxxxx
On Mon, Aug 17, 2009 at 11:14 PM, Christoph Hellwig<hch@xxxxxxxxxxxxx> wrote:
> 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.

Hi Chris, no problem. We're always busy ourself too. We will check out
the new fixes but we need some time to deploy them. We will take the
extra debug info with it just in case. We'll report back when we have
some news.

Cheers,
Tommy


>
> 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>