From: bfields@fieldses.org (J. Bruce Fields)
To: Anna Schumaker <schumakeranna@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: xfstests generic/263
Date: Tue, 27 Oct 2020 13:49:45 -0400 [thread overview]
Message-ID: <20201027174945.GC1644@fieldses.org> (raw)
Generic/263 is failing whenever client and server both supports
READ_PLUS.
I'm not even sure the failure is wrong. The NFS FALLOC operation doesn't
support those other other fallocate modes, are they implemented elsewhere in
the kernel or libc somehow? Anyway, odd that it would have anything to do with
READ_PLUS.
--b.
generic/263 109s ... [failed, exit status 1]- output mismatch (see /root/xfstests-dev/results//generic/263.out.bad)
--- tests/generic/263.out 2019-12-20 17:34:10.493343575 -0500
+++ /root/xfstests-dev/results//generic/263.out.bad 2020-10-27 13:43:41.968835322 -0400
@@ -1,3 +1,2018 @@
QA output created by 263
fsx -N 10000 -o 8192 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z
-fsx -N 10000 -o 128000 -l 500000 -r PSIZE -t BSIZE -w BSIZE -Z
+Seed set to 1
+main: filesystem does not support fallocate mode FALLOC_FL_KEEP_SIZE, disabling!
+main: filesystem does not support fallocate mode FALLOC_FL_ZERO_RANGE, disabling!
+main: filesystem does not support fallocate mode FALLOC_FL_COLLAPSE_RANGE, disabling!
...
(Run 'diff -u /root/xfstests-dev/tests/generic/263.out /root/xfstests-dev/results//generic/263.out.bad' to see the entire diff)
Ran: generic/263
Failures: generic/263
Failed 1 of 1 tests
next reply other threads:[~2020-10-27 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 17:49 J. Bruce Fields [this message]
2020-10-27 19:59 ` xfstests generic/263 Anna Schumaker
2020-10-27 20:05 ` J. Bruce Fields
2020-10-27 20:14 ` J. Bruce Fields
2020-11-05 20:52 ` J. Bruce Fields
2020-11-05 21:10 ` Anna Schumaker
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=20201027174945.GC1644@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=schumakeranna@gmail.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