this post was submitted on 10 Nov 2024
31 points (100.0% liked)

Linux

5230 readers
186 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
31
Debcow Optimizing Debian Packages For Copy-On-Write File-Systems (www.phoronix.com)
submitted 5 days ago by lemmee_in@lemm.ee to c/linux@programming.dev
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] LaggyKar@programming.dev 2 points 5 days ago

A normal copy consists of a program reading from one file and writing to another. There is no way for the filesystem to do a reflink in that case, it just sees that the program is reading and writing stuff. In order to do a reflink, the program must tell the filesystem what data should be "copied" to where using FICLONE or FICLONERANGE. Though some programs will do that by default if possible nowadays when copying files or when moving files between different subvolumes on the same partition, including the Coreutils cp, mv and install commands and some GUI file managers.