From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: Re: xfstests EBUSY on generic/32, generic/247
Date: Sun, 25 Feb 2018 18:54:51 -0500 [thread overview]
Message-ID: <20180225235451.GA12646@fieldses.org> (raw)
In-Reply-To: <20180223160350.GF15876@fieldses.org>
On Fri, Feb 23, 2018 at 11:03:50AM -0500, bfields wrote:
> Starting somewhere between v4.15-rc1 and v4.16-rc1, I'm getting sporadic
> failures: either on generic/32, with "pread64: Device or resource busy",
> or generic/247, on "mmap: Device or resource busy". Anyone else aware
> of this?
>
> Annoyingly, I haven't been able to reproduce yet by running just those
> tests, I only reproduce reliably with a 1-2 hour test run. I'll see if
> I can narrow it down any more....
And now I can't reproduce it at all. Maybe there was some problem with
the exported xfs filesystem? I guess I'm giving up for now.
--b.
prev parent reply other threads:[~2018-02-25 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 16:03 xfstests EBUSY on generic/32, generic/247 J. Bruce Fields
2018-02-25 23:54 ` J. Bruce Fields [this message]
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=20180225235451.GA12646@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).