On Thu, 2006-07-20 at 08:56 +1000, Nathan Scott wrote:
> On Wed, Jul 19, 2006 at 09:08:30AM +0100, Alistair John Strachan wrote:
> > On Tuesday 18 July 2006 23:57, Nathan Scott wrote:
> > [snip]
> > > > of programs fail in mysterious ways. I tried to recover using xfs_repair
> > > > but I feel that my partition is thorougly borked. Of course no data was
> > > > lost due to backups but still I'd like this bug to be fixed ;-)
> > >
> > > 2.6.18-rc1 should be fine (contains the corruption fix). Did you
> > > mkfs and restore? Or at least get a full repair run? If you did,
> > > and you still see issues in .18-rc1, please let me know asap.
> > Just out of interest, I've got a few XFS volumes that were created 24
> > months
> > ago on a machine that I upgraded to 2.6.17 about a month ago. I haven't
> > seen
> > any crashes so far.
> > Assuming I get the newest XFS repair tools on there, what's the
> > disadvantage
> > of repairing versus creating a new filesystem? What special circumstances
> > are
> > required to cause a crash?
> There should be no disadvantage to repairing. I will update the FAQ
> shortly to describe all the details of the problem, recommendations
> on how to address it, which kernel version is affected, etc.
this FAQ, is it this: http://oss.sgi.com/projects/xfs/faq.html#dir2 ?
(btw, it seems that while only in the TOC once, you have the same about
which version of xfsprogs should i use while doing the xfs_check ?