Description of problem: The following implementation might add significant value when working when using LVM for both HSM and SPM hosts. current pains: - lvm process is stuck in kernel - if certain lvm operation stuck (even read-only one), other lvm commands can't run and enter queue, since one of the lvm commands are stuck in kernel, it can only gets release using reboot, with this configuration, other lvm commands can still run, and host will not gets stuck. - HSM host tries to right to metadata - by design, hsm host should not write to metadata, we seen several cases where HSM hosts does change metadata, and altough we are in the process of clearing all cases, such configuration may save us from the first place. locking type = 4: Type 4 enforces read-only metadata and forbids any operations that might want to modify Volume Group metadata.
patch is from February, haven't been touched since may. is this still slated for 3.4?
(In reply to Itamar Heim from comment #1) > patch is from February, haven't been touched since may. > is this still slated for 3.4? Not clear.
Yeela, any update on this?
Please reopen if still relevant.