|To:||Eric Sandeen <sandeen@xxxxxxxxxxx>|
|Subject:||Re: 2.6.30 panic - xfs_fs_destroy_inode|
|From:||Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx>|
|Date:||Thu, 18 Jun 2009 09:55:18 +0200|
|Cc:||linux-xfs@xxxxxxxxxxx, Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>|
|User-agent:||Thunderbird 22.214.171.124 (Windows/20090302)|
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 126.96.36.199, 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.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||xfs_trans_read_buf error / xfs_force_shutdown with LVM snapshot and Xen kernel 2.6.18, Wolfram Schlich|
|Next by Date:||Re: xfs_trans_read_buf error / xfs_force_shutdown with LVM snapshot and Xen kernel 2.6.18, Eric Sandeen|
|Previous by Thread:||Re: 2.6.30 panic - xfs_fs_destroy_inode, Eric Sandeen|
|Next by Thread:||Re: 2.6.30 panic - xfs_fs_destroy_inode, Patrick Schreurs|
|Indexes:||[Date] [Thread] [Top] [All Lists]|