On Dec 4, 2009, at 2:21 AM, Jeffry Molanus wrote:
Actually, I asked about this a while ago only called it file-level
cloning. Consider you have 100VM's and you want to clone just one?
In my experience, cloning is done for basic provisioning, so how would
you get
to the case where you could not clone any particular VM?
-- richard
BTRFS added a specialized IOCTL() call to make the FS aware that it
has to clone this obviously saves copy time and dedup time.
Regards, Jeffry
-----Oorspronkelijk bericht-----
Van: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] Namens Roland Rambau
Verzonden: donderdag 3 december 2009 16:25
Aan: Per Baatrup
CC: zfs-discuss@opensolaris.org
Onderwerp: Re: [zfs-discuss] file concatenation with ZFS copy-on-
write
gang,
actually a simpler version of that idea would be a "zcp":
if I just cp a file, I know that all blocks of the new file
will be duplicates; so the cp could take full advantage for
the dedup without a need to check/read/write anz actual data
-- Roland
Per Baatrup schrieb:
"dedup" operates on the block level leveraging the existing FFS
checksums. Read "What to dedup: Files, blocks, or bytes" here
http://blogs.sun.com/bonwick/entry/zfs_dedup
The trick should be that the zcat userland app already knows that it
will generate duplicate files so data read and writes could be
avoided
all together.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
