2019-11-29 02:06:18

by J. Bruce Fields

[permalink] [raw]
Subject: generic/446 failure

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.