[linux-lvm] Very slow i/o after snapshotting

Zdenek Kabelac zkabelac at redhat.com
Tue Jul 9 18:42:29 UTC 2013

Dne 9.7.2013 19:59, matthew patton napsal(a):
> I don't know the internals of a VMware snapshot (aka journal disk) but what's the impact to writing to an LVM snapshot if the original is never written to again? Think of the original LV as a "golden master" and I create 10 snapshots of it and each DomU is presented with a snapshot device as it's /dev/hda. Does the indirection even work?
> I would have thought that the metadata in the snapshot device would have a bitmap (corresponding to specified "page" size) wherein the bitmap completely covered the original device and whenever a write got sent to the base block device (and the original copied to the snap) the flag would get updated such that reads to the snapshot device computes the "page" address of the desired block, checks the flag and if set, reads from the master device, otherwise find it in the snapshot (b-tree search? or hash+linked-list?)

As said above:

'Smart and cool' code is thin provisioning
'Old and very simple' is old snapshot code.

And you may try to guess which one of those two is  matching and even 
significantly surpassing your ideas ;)


More information about the linux-lvm mailing list