Subject: bug#60416: closed (Re: bug#60416: [PATCH] copy: attempt copy offload with sparse files)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 31 Dec 2022 00:24:02 +0000

Your bug report

#60416: Be more liberal using copy_file_range() with NFS mounted filesystems

which was filed against the coreutils package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
60416: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60416
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#60416: [PATCH] copy: attempt copy offload with sparse files
From: Pádraig Brady <[email-masked]>
To: Paul Eggert <[email-masked]>, Braiam <[email-masked]>, [email-masked]
Date: Sat, 31 Dec 2022 00:23:30 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

On 30/12/2022 22:32, Paul Eggert wrote:
> Thanks, looks good, please install.

Thanks for the review.
OP also posted good results.
Pushed with NEWS entry.
Marking this as done.

I may follow up with a related patch to
ensure we _don't_ use copy_file_range with --sparse=never.

cheers,
Pádraig

Subject: Be more liberal using copy_file_range() with NFS mounted filesystems
From: Braiam <[email-masked]>
To: [email-masked]
Date: Thu, 29 Dec 2022 12:04:38 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

When using a nfs export, cp seems to not try hard enough using
copy_file_range(). This was
the conclusion we arrived in this forum thread[1] at Truenas forums.
It was found a way to force
cp to use it, but it should not be necessary, since there are supposed
to be fallbacks.

I'm unsure if we found something that triggered the undesired behavior.

[1]: https://www.truenas.com/community/threads/nfs-does-not-support-server-side-copy-with-zfs.103309/post-712071

-- 
Braiam