2008-04-22 12:12:14 -0400, Brian J. Murrell: > On Tue, 2008-04-22 at 11:47 +0100, Stephane Chazelas wrote: > > > > but > > when you write to it, the system makes sure that unless it has > > been done already, the block you're modifying are being copied > > first from the "real" volume to COW volume before being modified > > in the "real" volume. > > And to be clear, the COW volumes of _all_ snapshots[1]. This is where > the snapshot scaling problem arises. > > Zumastor claim to have solved that with their snapshots. I'd love to > have time to play with it, indeed. [...] Indeed, actually I've spent the last 3 days trying to put zumastor (well actually ddsnap as I didn't use zumastor in the end) in place here. The fact that there are user space daemons involved in the process make it very difficult to use it for the root file system. I had to use a number of hacks for that. Also, it seems that you can't snapshot a live (mounted) file system as you would do with LVM2 unless you have setup that FS beforehand as a virtual ddsnap device (LVM2 is able to suspend the device, and reload it as a snapshot_origin for that, I couldn't manage to do the same with ddsnap). I also tried applying the patches to 2.6.25 and got some oops (2.6.24.2 is fine though). Once I've finalised it, I can post what I've come up with if anyone is interested. The least I can say is that I learnt a lot about grub2, initramfs-tools, device-mapper, raid/mdadm, lvm2 in the past few days ;). Cheers, Stephane _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
