On Wed, Oct 11, Alasdair G Kergon wrote: > The cow begins life as a real LV. > There is no way to distinguish it from other LVs. > > Changing that means changing the "create a snapshot" process into a single > LVM2 metadata transaction (or a pair of related transactions). Currently it's > two independent transactions - creating a new, empty LV; creating a snapshot > using that LV. Doing that would allow us to back out the change properly if > it's aborted too. Yes, that is probably the right thing to do. But I still need a solution for todays code. When we are clearing the exception store we know that the LV is going to be removed soon (and that udev will never find a valid filesystem in it). So why don't we tell udev that it shouldn't look at it in the first place. The easiest thing that we came up with is to mark the thing somehow. So we either use a different naming scheme for that LV (I don't like that idea) or we use a tag if possible. _______________________________________________ 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/
