| 1 |
On Wed, Mar 24, 2021 at 11:09 AM William Hubbs <williamh@g.o> wrote: |
| 2 |
> |
| 3 |
> On Wed, Mar 24, 2021 at 08:48:41AM +0100, Michał Górny wrote: |
| 4 |
> > |
| 5 |
> > What really can help is reflinking on filesystems supporting that. |
| 6 |
> |
| 7 |
> What really can help is more info instead of being terse like this. |
| 8 |
> Which filesystems support it? |
| 9 |
> |
| 10 |
|
| 11 |
According to Google right now: Btrfs, CIFS, NFS 4.2, OCFS2, overlayfs, and XFS |
| 12 |
|
| 13 |
Lizardfs ought to, but doesn't currently. zfs does not because clones |
| 14 |
only are supported at the dataset level. |
| 15 |
|
| 16 |
In any case, if you're using coreutils cp to do the copy, just pass |
| 17 |
--reflink=auto. Honestly, I have no idea why this isn't the default |
| 18 |
behavior. Who wouldn't want instant copy operations that consume zero |
| 19 |
space (aside from metdata)? If you're doing this in C or some other |
| 20 |
language you would need to see if they have a library call to do it |
| 21 |
easily - see man ioctl_ficlone. |
| 22 |
|
| 23 |
-- |
| 24 |
Rich |
Archives