Re: APFS cloning not working across volumes inside same container?
Re: APFS cloning not working across volumes inside same container?
- Subject: Re: APFS cloning not working across volumes inside same container?
- From: Vivek Verma <email@hidden>
- Date: Mon, 06 May 2019 10:10:12 -0700
> On May 6, 2019, at 6:21 AM, Thomas Tempelmann <email@hidden> wrote:
>
> I was just looking into making a Deduplication tool for macOS / APFS.
>
> One common scenario would be to deduplicate macOS systems on separate
> volumes. Like, for us developers who have several macOS versions on their
> computers for software testing purposes.
>
> I thought I could save a lot of space by having files inside /System and
> /Library share the same space by relying on APFS's cloning feature.
>
> However, when I tested copying a file from one volume to another volume, both
> being in the same APFS container (partition), Finder would still copy the
> data instead of doing the clone thing.
>
> Now I wonder if that's just a shortcoming of the Finder or a problem with the
> macOS API.
>
> After all, since APFS shares a single catalog between all volumes of its
> container, cloning should be possible across volumes, shouldn't it?
The think that most closely resembles the HFS catalog isn't shared amongst
volumes. clonefile(2) has the same restriction as link(2) and rename(2), it has
to be done within the same volume/mounted filesystem.
> --
> Thomas Tempelmann, http://apps.tempel.org/
> Follow me on Twitter: https://twitter.com/tempelorg
> Read my programming blog: http://blog.tempel.org/
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Filesystem-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden