Page MenuHomeSolus

our implementation of CP sigsegvs when copying in -a (archival) mode
Open, Needs More InfoPublicBUG

Description

Summary

the version of the Copy (cp) command we use is broken

Steps to reproduce

  1. cp -a a large folder from one drive to another
  2. wait

Expected result

For the copy to successfully go through

Actual result

it fails to copy with a sigsegv

Environment

  • Is system up to date? yes
  • Repo: Shannon, but the issue also exists in the unstable repo
  • Desktop Environment: Plasma

System details

Operating System: Solus 4.4
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Kernel Version: 6.3.12-241.current (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C37
System Version: 3.0

Other comments

See Also: the Rust Core Utils.

Event Timeline

ermo triaged this task as Needs More Info priority.Mon, Jul 31, 12:52 PM
ermo added a subscriber: ermo.

Thanks for the report.

1./ Does the size of the file relative to system RAM have any bearing on this? As in: How much larger is the file you're attempting to copy than your system RAM size? What is the smallest ratio between system RAM and Filesize at which this happens?

2./ What is the value of ulimit -a on your end? Does the issue happen with ulimit -s unlimited as well?

3./ For reference, does the same thing happen if you instead use rsync -a?

incapable of doing stuff ulimit, as i have switched to arch linux as i am one to do, should be default. However, i can confirm that i have 16gb system ram and swap available, but I was trying to copy a hundred gigs or more, (my entire home folder with a few steam games installed). Rsync and Rclone may both work but have separate issues.