[linux-lvm] Reserve space for specific thin logical volumes

Xen list at xenhideout.nl
Fri Sep 15 18:35:02 UTC 2017

matthew patton schreef op 15-09-2017 10:15:
>>  From the two proposed solutions (lvremove vs lverror), I think I 
>> would  prefer the second one.
> I vote the other way. :)

Unless you were only talking about lvremoving snapshots this is hugely 

You are throwing away a data collection?

> First because 'remove' maps directly to the DM equivalent action which
> brought this about.

That would imply you are only talking about snapshots, ?, even if 
dmsetup only creates a mapping, throwing away that mapping generally 
throws away data.

> With respect to freezing or otherwise stopping further I/O to LV being
> used by virtual machines, the only correct/sane solution is one of
> 'power off' or 'suspend'. Reaching into the VM to freeze
> individual/all filesystems but otherwise leave the VM running assumes
> significant knowledge of the VM's internals and the luxury of time.

That is simply user centric action that will in this case differ because 
a higher level function is better at cleanly killing something than a 
lower level function.

Same as that fsfreeze would probably be better in that sense than 

So in that sense, yes of course, I agree, that would be logical.

If you can do it clean, you don't have to do it rough.

In the same way you could have user centric action shut down webservers 
and so on. By user I mean administrator.

But for LVM team you can only provide mechanic that decides when action 
should be taken, and some default actions like possibly lverror and 
fsfreeze. You cannot decide what higher level interventions would be 
needed everywhere.

Of course clean shutdown would be ideal. This depends on system 

More information about the linux-lvm mailing list