From: Chuck Lever <chuck.lever@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: cel@kernel.org, Zorro Lang <zlang@redhat.com>,
linux-fsdevel@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: disable generic duperemove tests for NFS and others
Date: Mon, 9 Dec 2024 14:35:07 -0500 [thread overview]
Message-ID: <abc5b280-7d18-4438-851f-e333dd3e8361@oracle.com> (raw)
In-Reply-To: <Z1cHpXAS0S8R6_g4@infradead.org>
On 12/9/24 10:07 AM, Christoph Hellwig wrote:
> On Mon, Dec 09, 2024 at 10:00:58AM -0500, Chuck Lever wrote:
>> 2. How to disable this test on filesystems (like NFS) where duperemove
>> is not supported or where the test is not meaningful. The current check
>> for the presence of the duperemove executable is IMO inadequate.
>
> I've not looked at dupremove, but the name suggested it's de-duplicating
> and thus needs a working FIDEDUPERANGE ioctl. So the test should check
> for that using the _require_test_dedupe / _require_scratch_dedupe
> helpers. generic/{559,560,561} do that, so something either in these
> helpers is probably broken given that NFS rejects remap_file_range
> with REMAP_FILE_DEDUP, although a bit of tracing would be useful if
> there actually is something broken in NFS or the VFS.
It doesn't appear to be an NFS problem; duperemove is not even issuing
the ioctl as a toe-test to see if it will work.
I opened https://github.com/markfasheh/duperemove/issues/363
--
Chuck Lever
prev parent reply other threads:[~2024-12-09 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241208180718.930987-1-cel@kernel.org>
2024-12-09 18:45 ` [PATCH] fstests: disable generic duperemove tests for NFS and others Zorro Lang
2024-12-09 18:50 ` Chuck Lever
[not found] ` <Z1b1d3AXTxNhunYj@infradead.org>
[not found] ` <6dc5c09f-e1a2-4296-93d7-b2cda471a73f@oracle.com>
[not found] ` <Z1cHpXAS0S8R6_g4@infradead.org>
2024-12-09 19:35 ` Chuck Lever [this message]
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=abc5b280-7d18-4438-851f-e333dd3e8361@oracle.com \
--to=chuck.lever@oracle.com \
--cc=cel@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zlang@redhat.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