Leann, please look at the report. Comment #7 written on 2009-06-03 clearly indentifies the problem and has a link explaining details.
This bug is not reproducable. I got it on a high-usage-server after more than one year of usage and on a another box which isn't used heavily after few month. Another box which was used by a customer crashed after two weeks and we had a very hard time to recover the data. It happens whenever the XFS free blocks table gets a corruption. If you're lucky, the corruption isn't written to disk before the server crashes. Otherwise, the crash occurs every time the system requests free blocks and jumps into the corrupted area. (I'm neither a kernel not a xfs guy, so please don't slap me if this is not 100% correct.) This is clearly not "no-one-would-like-to-test-it-so-we-ignore-and- close-it" - bug, it's a really critical thing, but it has been finally resolved month ago. It should be easy to finally solve this issue on Ubuntu, too. All of us are currently lucky as long as you either get a power-outage or crash and ext3 "recovers" your filesystem bei killing all files or you're crash-safe but may run into the xfs-bug at any time. Best Regards, Sebastian -- XFS internal error xfs_trans_cancel at line 1164 of file /build/buildd/linux-2.6.27/fs/xfs/xfs_trans.c https://bugs.launchpad.net/bugs/294259 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
