On Sat, Jun 25, 2016 at 12:21:26AM -0500, Eric Sandeen wrote:
>
> > On Jun 24, 2016, at 11:44 PM, Eryu Guan <eguan@xxxxxxxxxx> wrote:
> >
> >> On Fri, Jun 24, 2016 at 05:37:10PM -0500, Eric Sandeen wrote:
> >>> On 3/4/16 5:23 AM, Eryu Guan wrote:
> >>> Hi,
> >>>
> >>> I noticed some xfstests failures while testing v4 XFS with latest
> >>> v4.5.0-rc1 xfsprogs on v4.5-rc6 kernel, and all these failures are gone
> >>> if I use v3.2.4 xfsprogs, or if test on v5 XFS.
> >>>
> >>> So either xfstests needs update or xfsprogs breaks something for non-crc
> >>> XFS. But I'm not sure which is which, so I post them out for broader
> >>> review.
> >>>
> >>> (All tests are checked with 'MKFS_OPTIONS="-m crc=0" ./check <sometest>')
> >>
> >> Eryu, sorry you didn't get a reply on this in March. We should have
> >> listened! ;) The patches I sent in the pat day or two should
> >
> > Thanks for looking at them! :)
> >
> >> fix some of these ...
> >>
> >>> == 1. xfs/032 fsck failure (xfs_db check) on ppc64 host ==
> >>
> >> but not this one. Do you still see this?
> >
> > My recent test with 4.7-rc4 kernel and latest xfsprogs (June 22nd) shows
> > xfs/032 passed on ppc64 host. But I'll retest to be sure.
>
> I wasn't thinking. Brian's recent sparse inode patches fix this one.
Confirmed xfsprogs v4.7-rc1 passed the test.
And xfs/244 is not ppc-specific, x86_64 fails it either. I think your
patch could fix it as well.
Thanks,
Eryu
|