From: Sam James <sam@gentoo.org>
To: 63850@debbugs.gnu.org
Subject: bug#63850: cp fails for files > 2 GB if copy offload is unsupported
Date: Fri, 02 Jun 2023 16:44:57 +0100 [thread overview]
Message-ID: <87h6rpn9uw.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hello,
Forwarding a downstream report of a behaviour change between
coreutils-9.1 and coreutils-9.3 from https://bugs.gentoo.org/907474.
The reporter bisected it to 093a8b4bfaba60005f14493ce7ef11ed665a0176
("copy: fix --reflink=auto to fallback in more cases", see bug#62404)
and gave strace output showing:
```
fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
copy_file_range(3, NULL, 4, NULL, 9223372035781033984, 0) = 2147479552
copy_file_range(3, NULL, 4, NULL, 9223372035781033984, 0) = -1 EINVAL
(Invalid argument)
```
"""
When I try to copy a large file (> 2 GB) like so:
cp --debug file_a file_b
output looks like this:
'file_a' -> 'file_b'
cp: error copying 'file_a' to 'file_b': Invalid argument
copy offload: unsupported, reflink: unsupported, sparse detection: no
Afterwards file_b has a size of 2147479552 bytes (= 2G - 4K).
On another system (with newer kernel version) it looks like this:
cp --debug file_a file_b
'file_a' -> 'file_b'
copy offload: yes, reflink: unsupported, sparse detection: no
"""
Let me know if you need further information, although there's
some more on the downstream Gentoo bug I linked.
Apparently this is only happening w/ the 4.19.x kernels.
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2023-06-02 15:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 15:44 Sam James [this message]
2023-06-02 16:31 ` bug#63850: cp fails for files > 2 GB if copy offload is unsupported Pádraig Brady
2023-06-03 1:02 ` Mike Gilbert
2023-06-03 5:25 ` Pádraig Brady
2023-06-03 6:05 ` Paul Eggert
2023-06-03 13:54 ` Mike Gilbert
2023-06-03 17:12 ` Arsen Arsenović via GNU coreutils Bug Reports
2023-06-06 4:48 ` Paul Eggert
2023-06-06 5:07 ` Paul Eggert
2023-06-06 5:09 ` Sam James
2023-06-06 5:26 ` Sam James
2023-06-06 5:48 ` Paul Eggert
2023-06-06 9:53 ` Pádraig Brady
2023-06-06 10:02 ` Sam James
2023-06-06 10:27 ` Pádraig Brady
2023-06-07 19:13 ` Paul Eggert
2023-06-07 19:21 ` Sam James
2023-06-07 19:44 ` Paul Eggert
2023-06-08 11:28 ` Arsen Arsenović via GNU coreutils Bug Reports
2023-06-08 17:44 ` Paul Eggert
2023-06-03 18:39 ` Pádraig Brady
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6rpn9uw.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=63850@debbugs.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).