On Thu, 24 Apr 2008, Larry Dickson wrote:
> There's an almost trivial variant on this, where you keep the
> (read-only) snapshots in a time-ordered sequence, and freeze the last
> snapshot COW at the same moment as you start the next snapshot. Then writing
> only ever hits the new snapshot COW, and reading from any older snapshot
> (virtual) volume involves figuring out which is the first after that to hold
> the block, but still involves reading only one block. I wonder why LVM does
> not do this. Perhaps Zumastor does? Or somebody else?
Then you can't delete an older snapsnot until you delete all newer ones.
Zumastor works by using one COW table shared between all snapshots
for a volume. Blocks are added to the COW in time order. The origin
ignores COW blocks before the last time point (block offset), writing a new COW
block for any modified since that time point. The snapshots also use
timepoints in a way that is straightforward, but I don't want to think
about it at the moment :-)
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
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/
