* generic/446 failure
@ 2019-11-29 2:05 J. Bruce Fields
0 siblings, 0 replies; only message in thread
From: J. Bruce Fields @ 2019-11-29 2:05 UTC (permalink / raw)
To: Trond Myklebust, Anna Schumaker; +Cc: linux-nfs
I'm seeing a failure like:
generic/446 32s ... - output mismatch (see /root/xfstests-dev/results//generic/446.out.bad)
--- tests/generic/446.out 2019-09-18 17:28:00.826721481 -0400
+++ /root/xfstests-dev/results//generic/446.out.bad 2019-11-28 18:56:36.583719464 -0500
@@ -1,2 +1,7 @@
QA output created by 446
+fallocate: Resource temporarily unavailable
+fallocate: Resource temporarily unavailable
+fallocate: Resource temporarily unavailable
+fallocate: Resource temporarily unavailable
+fallocate: Resource temporarily unavailable
Silence is golden
...
A bisect pins it on:
0e0cb35b417f NFSv4: Handle NFS4ERR_OLD_STATEID in CLOSE/OPEN_DOWNGRADE
Have you seen this before?
I took a quick look at a network trace to see if there were
ALLOCATE or DEALLOCATE failures, but there weren't. The problem doesn't
reproduce when the test is run under strace. That's all I've tried.
--b.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-11-29 2:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-29 2:05 generic/446 failure 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).