[Top] [All Lists]

Re: XFS internal error xfs_iformat(realtime) even after xfs_repair.

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: XFS internal error xfs_iformat(realtime) even after xfs_repair.
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 2 Feb 2011 10:04:13 +1100
Cc: Ajeet Yadav <ajeet.yadav.77@xxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20110201212832.GA1836@xxxxxxxxxxxxx>
References: <AANLkTin=nqXCVJRgqBuTDx6nxMx1GLiG2DortJG+pz2L@xxxxxxxxxxxxxx> <20110118045730.GU28803@dastard> <AANLkTikc-_dZvpu6Yb-FNJVVWqhmsC4OgVZ8gj0mRx-y@xxxxxxxxxxxxxx> <AANLkTimuB71cTrW3gsSPq=HhFgHC=5xCZAMMxNE97F06@xxxxxxxxxxxxxx> <20110201041202.GL11040@dastard> <20110201212832.GA1836@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Tue, Feb 01, 2011 at 04:28:32PM -0500, Christoph Hellwig wrote:
> > It will be in the next release, whenever we make that.
> > 
> > I've got to finish of the sync of the userspace/kernel code, there's
> > a few fixes already in the -dev branch as well, we need to pick up
> > the FIEMAP changes to xfs_io, and so on. We probably should get t???is
> > all done and plan for a new release in the next few weeks...
> I'm a bit concerned about the coverage of the libxfs resync.  My
> preference would be to get out a minor release focusses at the repair
> fixes, then merge the resync to master directly after release and make
> sure it gets into all the test setups for a while before it gets
> released.

Sure, I have no problem with that - this is the first mention of a
new release and I was just mentioning everything that is happening
at the moment. Doing a point release with all the known
fixes before the large sync makes sense...


Dave Chinner

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