From: bfields@fieldses.org (J. Bruce Fields)
To: linux-nfs@vger.kernel.org
Subject: sporadic generic/154 failure
Date: Mon, 23 Aug 2021 10:48:02 -0400 [thread overview]
Message-ID: <20210823144802.GA883@fieldses.org> (raw)
I'm seeing generic/154 failing sometimes.
It does a "cp --reflink" (which uses FI_CLONE, which results in a
->remap_file_range call that NFS maps to the CLONE operation), then
overwriting parts of the fire, and checking free blocks (with "stat -f
/path -c "%f") at various points, and failing when the number of free
blocks is outside an expected range.
I don't know if it might be some caching issue, or something about how
NFS reports free blocks.
Honestly it looks unlikely to be critical, so for now I'm ignoring
it....
--b.
next reply other threads:[~2021-08-23 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:48 J. Bruce Fields [this message]
2021-08-23 15:06 ` sporadic generic/154 failure Trond Myklebust
2021-08-23 15:11 ` bfields
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=20210823144802.GA883@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.