ZFS zfs promote

[Ofloo]

For some reason, I remember promote to something else. Basically when I clone a snapshot and promote it it should become it's own zfs dataset however for some reason for me it switches around the clone?

  snapshots
    tank/bhyve/tea@2022-09-25-12:33:33    68K    Sun Sep 25 12:33 2022
    tank/bhyve/tea/disk0@2022-09-25-12:33:33    0B    Sun Sep 25 12:33 2022

  clone-origin
    tank/bhyve/aet@2022-09-25-12:20:47

#

after promoting the filesystem

  snapshots
    tank/bhyve/aet@2022-09-25-12:29:41    76K    Sun Sep 25 12:29 2022
    tank/bhyve/aet/disk0@2022-09-25-12:29:41    0B    Sun Sep 25 12:29 2022

  clone-origin
    tank/bhyve/tea@2022-09-25-12:20:47

Maybe that is what it is supposed to do but how do I make it so that a cloned dataset becomes it's own dataset.

 

[Eric A. Borisch]

This is what promotion does; one is always the origin, the other the child.

If you want a fully separate filesystem (no sharing of blocks to store shared data/history) you need to use send/recv.

 

[loveydovey]

A promoted dataset becomes it's own dataset...and you can destroy the snapshot(s) it was promoted from. Then all that remains is sharing of data blocks behind the scenes at the ZFS layer. You can uncouple then with zfs send/recv, like Borisch suggested, but that literally duplicates all the data that was shared at the block level and can balloon the size of the dataset.