From 58eedf062d79adafbd5c1ef52995a5f168a4b065 Mon Sep 17 00:00:00 2001 From: "lena.wildervanck@4b6aac156870f72a36b090e210e4747f702b69cb" Date: Fri, 18 Nov 2022 22:02:20 +0000 Subject: [PATCH] Add another reflink support request --- ...Write__47__reflink__47__clonefile_support_on_macOS.mdwn | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 doc/todo/Copy-on-Write__47__reflink__47__clonefile_support_on_macOS.mdwn diff --git a/doc/todo/Copy-on-Write__47__reflink__47__clonefile_support_on_macOS.mdwn b/doc/todo/Copy-on-Write__47__reflink__47__clonefile_support_on_macOS.mdwn new file mode 100644 index 0000000000..e70a5b7e6c --- /dev/null +++ b/doc/todo/Copy-on-Write__47__reflink__47__clonefile_support_on_macOS.mdwn @@ -0,0 +1,7 @@ +Thank you for your previous message here: [[/todo/Copy-on-Write__47__reflink_support_for_unlocked_files/]]. + +I indeed discovered it was done for Linux after I posted it, but macOS with APFS also supports reflinks, under the `-c` (clonefile) option, which does the same as the `--reflink=always` option on Linux. + +The biggest problem is that there is no auto option, but in theory it’s possible to first try the clone option, and then fall back if it doesn’t work, although that would be inefficient. + +I can try to code something, although I am not that proficient in Haskell, or run test code if needed on macOS 12.