https://bugs.kde.org/show_bug.cgi?id=328709
--- Comment #15 from tagwer...@innerjoin.org --- (In reply to Marcus Sundman from comment #14) > ... on btrfs ... I think if you do "df" before and after the copy, you'll see that the copy has not actually taken up space. It looks as if "du" is clever enough not to double count space "taken" by hardlinked files but isn't yet up to do the same job for reflinked ones. Maybe "btrfs filesystem du ...". I can see there's a slight difference in behaviour in that after a "ln a b", if you edit either of the files you change them "both". After a "cp reflink=auto a b", if you edit either, you'll get two distinct copies. Question is, assuming you are on BTRFS, might this be good enough? -- You are receiving this mail because: You are watching all bug changes.
