From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Christoph Hellwig <hch@infradead.org>, <trond.myklebust@primarydata.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: xfstests generic/285 fails reliably on Trond's linux-next branch
Date: Thu, 28 Jul 2016 15:36:04 -0400 [thread overview]
Message-ID: <d67d77f3-9df9-4f02-354b-85cc46a5f9c5@Netapp.com> (raw)
In-Reply-To: <20160728144641.GA28753@infradead.org>
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
next prev parent reply other threads:[~2016-07-28 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 8:18 xfstests generic/285 fails reliably on Trond's linux-next branch Christoph Hellwig
2016-07-28 14:46 ` Christoph Hellwig
2016-07-28 19:36 ` Anna Schumaker [this message]
2016-08-01 13:28 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d67d77f3-9df9-4f02-354b-85cc46a5f9c5@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox