[Top] [All Lists]

Re: XFS breakage in 2.6.18-rc1

To: Torsten Landschoff <torsten@xxxxxxxxxx>
Subject: Re: XFS breakage in 2.6.18-rc1
From: Nathan Scott <nathans@xxxxxxx>
Date: Thu, 20 Jul 2006 09:09:45 +1000
Cc: linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20060719211402.GA1133@stargate.galaxy>; from torsten@debian.org on Wed, Jul 19, 2006 at 11:14:02PM +0200
References: <20060718222941.GA3801@stargate.galaxy> <20060719085731.C1935136@wobbly.melbourne.sgi.com> <20060719211402.GA1133@stargate.galaxy>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Wed, Jul 19, 2006 at 11:14:02PM +0200, Torsten Landschoff wrote:
> On Wed, Jul 19, 2006 at 08:57:31AM +1000, Nathan Scott wrote:
> > 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).
> That probably the cause of my problem. Thanks for the info!
> BTW: I think there was nothing important on the broken filesystems, but
> I'd like to keep what's still there anyway just in case... How would you
> suggest should I copy that data? I fear, just mounting and using cp 
> might break and shutdown the FS again, would xfsdump be more
> appropriate?

Yeah, xfsdumps not a bad idea, the interfaces it uses may well
be able to avoid the cases that trigger shutdown.  Otherwise it
is a case of identifying the problem directory inode (the inum
is reported in the shutdown trace) and avoiding that path when
cp'ing - you can match inum to path via xfs_ncheck.

> Thanks for XFS, I am using it for years in production servers!

Thanks for the kind words, they're much appreciated at times
like these. :-]



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