On Fri, 2004-11-19 at 11:39 -0500, Ming Zhang wrote: > Hi, I wonder if there are any thought about a relocate on write policy > for snapshot instead of copy on write policy used now? > > instead of copy old one to snapshot, overwrite old one with new one, 2 > writes and 1 reads. it is possible that write new data to a usused > location directly. > > i know later remove a snaphot will be a little trouble, but there must > be some way to get around it. > > just a rough thought, any comment? > I thought the way it worked now was for snapshot LV to be marked as the "active destination" for all new writes to the logical volume. On write, the data isn't copied, just the metadata is changed to reflect which physical extent the block is now located on, and the old one is then reallocated as part of the snapshot. Am I wrong? -- Clint Byrum <cbyrum@spamaps.org> _______________________________________________ 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/
