2011/7/11 Stephane Chazelas <stephane_chazelas@xxxxxxxx>: > 2011-07-11 02:00:51 +0200, krzf83@xxxxxxxxx : >> Documentation says that btrfs-image zeros data. Feature request is for >> disabling this. btrfs-image could be used to copy filesystem to >> another drive (for example with snapshots, when copying it file by >> file would take much longer time or acctualy was not possible >> (snapshots)). btrfs-image in turn could be used to actualy shrink loop >> devices/sparse file containing btrfs - by copying filesystem to new >> loop device/sparse file. >> >> Also it would be nice if copying filesystem could occour without >> intermediate dump to a file... > [...] > > I second that. > > See also > http://thread.gmane.org/gmane.comp.file-systems.btrfs/9675/focus=9820 > for a way to transfer btrfs fs. > > (Add a layer of "copy-on-write" on the original devices (LVM > snapshots, nbd/qemu-nbd cow...), "btrfs add" the new device(s) > and then "btrfs del" of the cow'ed original devices. > > -- > Stephane > Copying on block level (dd, lvm) is old trick, however this takes same ammount of time regardless of actual space used in filesystem. Hence this feature request. Images inside filesystem can copy only actualy used data and metadata, which dramaticly reduces copy times in large volumes that are not filled up... -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html