* xfstests EBUSY on generic/32, generic/247
@ 2018-02-23 16:03 J. Bruce Fields
2018-02-25 23:54 ` J. Bruce Fields
0 siblings, 1 reply; 2+ messages in thread
From: J. Bruce Fields @ 2018-02-23 16:03 UTC (permalink / raw)
To: linux-nfs
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....
--b.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: xfstests EBUSY on generic/32, generic/247
2018-02-23 16:03 xfstests EBUSY on generic/32, generic/247 J. Bruce Fields
@ 2018-02-25 23:54 ` J. Bruce Fields
0 siblings, 0 replies; 2+ messages in thread
From: J. Bruce Fields @ 2018-02-25 23:54 UTC (permalink / raw)
To: linux-nfs
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-02-25 23:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-23 16:03 xfstests EBUSY on generic/32, generic/247 J. Bruce Fields
2018-02-25 23:54 ` J. Bruce Fields
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).