From: Trond Myklebust <trondmy@hammerspace.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: sporadic generic/154 failure
Date: Mon, 23 Aug 2021 15:06:21 +0000 [thread overview]
Message-ID: <e3ea3f425fb8765d13e7b73aaf7df5022c4183e5.camel@hammerspace.com> (raw)
In-Reply-To: <20210823144802.GA883@fieldses.org>
On Mon, 2021-08-23 at 10:48 -0400, J. Bruce Fields wrote:
> 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....
>
XFS backend? It could be speculative preallocation. The fact that NFS
can defer closing the file (either due to delegations or due to the
NFSv3 file cache) typically results in it taking longer for XFS to free
up the blocks it preallocated. That again means it takes longer for the
'space used' to settle to the correct final value.
https://linux-xfs.oss.sgi.narkive.com/jjjfnyI1/faq-xfs-speculative-preallocation
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2021-08-23 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 14:48 sporadic generic/154 failure J. Bruce Fields
2021-08-23 15:06 ` Trond Myklebust [this message]
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=e3ea3f425fb8765d13e7b73aaf7df5022c4183e5.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox