is the patch now in 22.214.171.124?
The more exact question is: Does XFS (and xfsprogs) work perfectly now again?
My backup works with xfsdump, so it would be a disaster when this does not work.
Thanks for your information!
Am Fri, 27 Aug 2010 21:40:55 +1000
schrieb Dave Chinner <david@xxxxxxxxxxxxx>:
> On Fri, Aug 27, 2010 at 01:18:20PM +0200, Iustin Pop wrote:
> > On Tue, Aug 17, 2010 at 09:45:50PM +1000, Dave Chinner wrote:
> > > My fault. I screwed up the btree lookup for the inode validation.
> > > Can you test the patch below?
> > I just see that 126.96.36.199 has been released, but it doesn't include this
> > fix (as far as I can see). Could it be send for inclusion into the next
> > stable please (yes, it fixes the issue for me too).
> The commit is now upstream, it had a "cc: stable@xxxxxxxxxx" in it,
> so it should get automatically queued for inclusion in the next
> stable kernel release. If I don't see it appear in Greg's stable
> queue once he starts processing the commits for the next stable
> release, I'll chase it up....