From: Patrick Schreurs <patrick@news-service.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@oss.sgi.com, Tommy van Leeuwen <tommy@news-service.com>,
Lachlan McIlroy <lmcilroy@redhat.com>,
Eric Sandeen <sandeen@sandeen.net>
Subject: Re: 2.6.30 panic - xfs_fs_destroy_inode
Date: Tue, 30 Jun 2009 22:13:57 +0200 [thread overview]
Message-ID: <4A4A7205.6010101@news-service.com> (raw)
In-Reply-To: <20090623171305.GB23971@infradead.org>
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?
Thanks.
-Patrick
Christoph Hellwig wrote:
> On Tue, Jun 23, 2009 at 04:17:13AM -0400, Lachlan McIlroy wrote:
>> It looks to me like xfs_reclaim_inode() has returned EAGAIN because the
>> XFS_RECLAIM flag was set on the xfs inode. This implies we are trying
>> to reclaim an inode that is already in the process of being reclaimed.
>> I'm not sure how this happened but it could be a simple case of ignoring
>> this error since the reclaim is already in progress.
>
> Well, having the reclaim already in progress means we're racing here.
> And I suspect this fits into the other bugs with possibly duplicat
> inodes we see after the inode+xfs_inode unification.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-30 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 17:04 2.6.30 panic - xfs_fs_destroy_inode Patrick Schreurs
2009-06-17 21:31 ` Eric Sandeen
2009-06-18 7:55 ` Patrick Schreurs
2009-06-20 10:18 ` Patrick Schreurs
2009-06-20 13:29 ` Eric Sandeen
2009-06-20 16:31 ` Patrick Schreurs
2009-06-23 7:24 ` Patrick Schreurs
2009-06-23 8:17 ` Lachlan McIlroy
2009-06-23 17:13 ` Christoph Hellwig
2009-06-30 20:13 ` Patrick Schreurs [this message]
2009-06-30 20:42 ` Christoph Hellwig
2009-07-20 19:19 ` Patrick Schreurs
2009-07-20 20:14 ` Christoph Hellwig
2009-07-01 12:44 ` Christoph Hellwig
2009-07-02 7:09 ` Tommy van Leeuwen
2009-07-02 17:31 ` Patrick Schreurs
2009-07-21 14:12 ` Christoph Hellwig
2009-07-22 8:55 ` Tommy van Leeuwen
2009-08-17 21:14 ` Christoph Hellwig
2009-08-20 12:24 ` Tommy van Leeuwen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4A7205.6010101@news-service.com \
--to=patrick@news-service.com \
--cc=hch@infradead.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lmcilroy@redhat.com \
--cc=sandeen@sandeen.net \
--cc=tommy@news-service.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox