[Top] [All Lists]

Re: XFS breakage in 2.6.18-rc1

To: Alistair John Strachan <s0348365@xxxxxxxxxxxx>
Subject: Re: XFS breakage in 2.6.18-rc1
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 20 Jul 2006 08:56:36 +1000
Cc: Torsten Landschoff <torsten@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <200607190908.30727.s0348365@xxxxxxxxxxxx>; from s0348365@xxxxxxxxxxxx on Wed, Jul 19, 2006 at 09:08:30AM +0100
References: <20060718222941.GA3801@xxxxxxxxxxxxxxx> <20060719085731.C1935136@xxxxxxxxxxxxxxxxxxxxxxxx> <200607190908.30727.s0348365@xxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
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.



<Prev in Thread] Current Thread [Next in Thread>