Now that 207 is fixed the next test starts failing.. 285 is
the SEEK_HOLE/DATA sanity check, which might help with figuring out
which of the recent changes introduced it.
On Thu, Jul 21, 2016 at 01:18:02AM -0700, Christoph Hellwig wrote:
> Now that 207 is fixed the next test starts failing.. 285 is
> the SEEK_HOLE/DATA sanity check, which might help with figuring out
> which of the recent changes introduced it.
A week later this still fails with the linux-next branch. Plain NFSv4.2
against a Linux/XFS server. The 285.full file documenting the failures
is attached below:
Hi Christoph,
On 07/28/2016 10:46 AM, Christoph Hellwig wrote:
> On Thu, Jul 21, 2016 at 01:18:02AM -0700, Christoph Hellwig wrote:
>> Now that 207 is fixed the next test starts failing.. 285 is
>> the SEEK_HOLE/DATA sanity check, which might help with figuring out
>> which of the recent changes introduced it.
>
> A week later this still fails with the linux-next branch. Plain NFSv4.2
> against a Linux/XFS server. The 285.full file documenting the failures
> is attached below:
>
What mount options are you using? The test passes for me on xfs, btrfs, and ext4.
Thanks,
Anna
On Thu, Jul 28, 2016 at 03:36:04PM -0400, Anna Schumaker wrote:
> What mount options are you using? The test passes for me on xfs, btrfs, and ext4.
No mount options at all - just forcing 4.2 with a small patch to
super.c.
I've tried to bisect the issue, but I now see it with Linux 4.7-rc2 as
well. I did upgrade xfstests in the meantime, so I'll see if that
caused the issue, or if it's something that's new in Linux 4.7-rc2 and
Tronds earlier tree was using an older baseline.