| To: | Patrick Schreurs <patrick@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.6.30 panic - xfs_fs_destroy_inode |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 30 Jun 2009 16:42:56 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Lachlan McIlroy <lmcilroy@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, Tommy van Leeuwen <tommy@xxxxxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx> |
| In-reply-to: | <4A4A7205.6010101@xxxxxxxxxxxxxxxx> |
| References: | <4A408316.2070903@xxxxxxxxxxxxxxxx> <1587994907.388291245745033392.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20090623171305.GB23971@xxxxxxxxxxxxx> <4A4A7205.6010101@xxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Tue, Jun 30, 2009 at 10:13:57PM +0200, Patrick Schreurs wrote: > 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? For now please downgrade to the latest 2.6.28, yes. I hope I will have time and machine ressources to dig deeper into the problem this week. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.30 panic - xfs_fs_destroy_inode, Patrick Schreurs |
|---|---|
| Next by Date: | Re: Seg fault during xfs repair (segmentation fault / segv), Jesse Stroik |
| Previous by Thread: | Re: 2.6.30 panic - xfs_fs_destroy_inode, Patrick Schreurs |
| Next by Thread: | This is about, valentina . fiket |
| Indexes: | [Date] [Thread] [Top] [All Lists] |