xfs
[Top] [All Lists]

Re: 2.6.30 panic - xfs_fs_destroy_inode

To: Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>
Subject: Re: 2.6.30 panic - xfs_fs_destroy_inode
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sat, 20 Jun 2009 08:29:06 -0500
Cc: "linux-xfs@xxxxxxxxxxx" <linux-xfs@xxxxxxxxxxx>, Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>
In-reply-to: <4A3CB765.8040600@xxxxxxxxxxxxxxxx>
References: <4A392213.4020200@xxxxxxxxxxxxxxxx> <4A3960A0.8090707@xxxxxxxxxxx> <4A39F2E6.5020205@xxxxxxxxxxxxxxxx> <4A3CB765.8040600@xxxxxxxxxxxxxxxx>
Others aren't hitting this, what sort of workload are you running when you hit it?

I have not had time to look at it yet but some sort of testcase may greatly help.

-Eric

On Jun 20, 2009, at 5:18 AM, Patrick Schreurs <patrick@news- service.com> wrote:

Unfortunately another panic. See attachment.

Would love to receive some advice on this issue.

Thanks in advance.

-Patrick

Patrick Schreurs wrote:
Eric Sandeen wrote:
Patrick Schreurs wrote:
Hi all,

We are experiencing kernel panics on servers running 2.6.29(.1) and 2.6.30. I've included two attachments to demonstrate.

The error is:
Kernel panic - not syncing: xfs_fs_destroy_inode: cannot reclaim ...

OS is 64bit Debian lenny.

Is this a known issue? Any comments on this?

It's not known to me, was this a recent upgrade?  (IOW, did it start
with .29(.1)?
We've seen this on 2 separate servers. It probably happened more often, but we didn't captured the panic message. One server was running 2.6.29.1, the other server was running 2.6.30. Currently we've updated all similar servers to 2.6.30. If we can provide you with more details to help fix this issue, please let us know.
-Patrick
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
<sb06-20090619.png>

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