Reserve space for specific thin logical volumes
A message that is not in the archive (sent off-list or not yet received): [email protected]
'yes'
The filesystem may not be resident on the hypervisor (dom0) so 'dmsetup suspend' is probably more apropos. How well that propagates upward to the unwary client VM remains to be seen. But if one were running a NFS server using thin+xfs/ext4 then the 'fsfreeze' makes sense.
Dne 13.9.2017 v 02:04 matthew patton napsal(a):
Quoted 4 lines
'yes'
The filesystem may not be resident on the hypervisor (dom0) so 'dmsetup suspend' is probably more apropos. How well that propagates upward to the unwary client VM remains to be seen. But if one were running a NFS server using thin+xfs/ext4 then the 'fsfreeze' makes sense.
lvm2 is not 'expecting' someone will touch lvm2 controlled DM devices.
If you suspend thinLV with dmsetup - you are in big 'danger' of freezing further lvm2 processing - i.e. command will try scan device list and will get blocked on suspend (even if lvm2 checks for 'suspended' dm devices to skip then via lvm.conf setting - there is clear race)
So any solution which works outside lvm2 and changes dm table outside of lvm2 locking mechanism is hardly supportable - it can be used as 'last weapon' - but it should be clear to user - that next proper step is to reboot the machine....
Regards
Zdenek