Messages in this thread | | | Date | Thu, 20 Jul 2006 11:13:57 -0400 | From | "Kevin Radloff" <> | Subject | Re: FAQ updated (was Re: XFS breakage...) |
| |
On 7/20/06, Nathan Scott <nathans@sgi.com> wrote: > On Wed, Jul 19, 2006 at 12:21:08PM +0200, Kasper Sandberg wrote: > > On Wed, 2006-07-19 at 08:57 +1000, Nathan Scott wrote: > > > On Wed, Jul 19, 2006 at 12:29:41AM +0200, Torsten Landschoff wrote: > > > > > > > > Jul 17 07:33:53 pulsar kernel: xfs_da_do_buf: bno 16777216 > > > > Jul 17 07:33:53 pulsar kernel: dir: inode 54526538 > > > > > > I suspect you had some residual directory corruption from using the > > > 2.6.17 XFS (which is known to have a lurking dir2 corruption issue, > > > fixed in the latest -stable point release). > > Correction there - no -stable exists with this yet, I guess that'll > be 2.6.17.7 once its out though. > > > what action do you suggest i do now? > > I've captured the state of this issue here, with options and ways > to correct the problem: > http://oss.sgi.com/projects/xfs/faq.html#dir2 > > Hope this helps.
I actually tried the xfs_db method to fix my / filesystem (as you had outlined in http://marc.theaimsgroup.com/?l=linux-kernel&m=115070320401919&w=2), and while it's quite possible that I screwed it up, after a subsequent xfs_repair run (which completed successfully and moved lots of stuff to /lost+found, as I would expect), the XFS code had serious problems with various parts of my filesystem (like "ls /lost+found", which would cause lots of errors to be logged, although not a complete fs shutdown). After another run through xfs_repair resulted in a filesystem that would no longer even successfully boot.
Unfortunately it was a mostly-full 74GB big-/ partition on my primary machine (a laptop), so I don't have a dump of it for you and my report is probably pretty useless. :( But on the bright side, virtually all of the filesystem was otherwise intact and I was able to get all my data off before rebuilding my system.
-- Kevin 'radsaq' Radloff radsaq@gmail.com http://thesaq.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |