On Tue, 2008-06-03 at 15:26 -0400, Mikulas Patocka wrote: > Hi > Merging allows you to copy data in snapshot back to the origin device. Cool. > During merging, aby typo? ------------^^^ > reads and writes to the origin device are identical to > accesses to the merging snapshots. So the origin looks 100% merged as soon as the merging starts? > There may be multiple snapshots while one of them is being merged --- > exceptions in other snapshots are being allocated and there snapshots are > kept stable. So basically, before blocks are copied up from the merging snapshot to the origin, the blocks to be overwritten (in the origin) are first copied down to other snapshots of the same origin? Is it smart about a block that is to be copied up to the origin being the same as the corresponding blocks in peer snapshots? By "smart" I mean erase the block in the peer's snapshot and put back the pointer up to the origin. A pedantic example would be to create an origin, O1 and then a snapshot of O1 called S1. Make a bunch of changes to S1 and then create another snapshot of O1 called S2 and then block copy from S1 to S2 (presumably, although I don't know for sure, S2 only contains the same changed blocks as S1). Now if you merge S1 up to O1, ideally S2 should be "empty". > Don't try to concurrently merge more than one snapshot Heh. b.
Description: This is a digitally signed message part