| To: | Richard Ems <Richard.Ems@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS internal error xfs_btree_check_lblock |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 21 Jul 2008 11:11:19 -0500 |
| Cc: | markgw@xxxxxxx, xfs@xxxxxxxxxxx, "Bill O'Donnell" <billodo@xxxxxxx> |
| In-reply-to: | <488457F3.2050405@cape-horn-eng.com> |
| References: | <4880AEF8.2080906@cape-horn-eng.com> <48815AA6.3080102@sgi.com> <488457F3.2050405@cape-horn-eng.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.14 (Macintosh/20080421) |
Richard Ems wrote: > Mark Goodwin wrote: >> Hi Richard, >> >> this looks like XFS b-tree corruption of some sort. We have some patches >> that should help here. The patches are being back-ported to SLES10 and >> should also apply to OpenSUSE. We should have something ready early next >> week. > > Thanks Mark. The most annoying thing is that, after many repairs, it's > working again! But my big question is ... for how long? How stable is > the filesystem now? Should I better recreate it? WHY did this happen? > Why did the FS fail again after some repairs? 8( > > Where can I get more info about these patches? Is there a developer > mailing list? Or some webpage to follow the development progress? This *is* the developer mailing list, and I am honestly a bit frustrated that said bugs & patches are not being aired & reviewed in public, honestly. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS internal error xfs_btree_check_lblock, Russell Cattelan |
|---|---|
| Next by Date: | xfsrestore over ssh?, Richard Hartmann |
| Previous by Thread: | Re: XFS internal error xfs_btree_check_lblock, Richard Ems |
| Next by Thread: | Re: XFS internal error xfs_btree_check_lblock, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |