introduce lvm forcevg option to forcibly deactivate the whole vg
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 1 patch 0 repliesNew
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Patch review 0/1] introduce lvm forcevg option to forcibly deactivate the whole vg
Quoted 2 lines
Hmm - but script seems to be calling apps like umount - that isn't going cause issues ?
forcevg is not doing unmount because it would have problems (and we wouldn't want to modify the system's filesystem namespace.)
Quoted 10 lines
Quoted 6 lines
Our particular use of this is as a helper script that sanlock runs when the device holding the leases goes away, and the machine will be imminently reset by the watchdog if we can't disable the LVs. Given those unique circumstances, we don't care about other lvm commands. Is this case is so specialized that it should be put in a separate script rather than in blkdeactivate?
Wondering if there could be something for sharing for possibly usage in cases user wants to drop devices when thin-pool gets 'too full' and devices should be forcibly dropped even when they are in use...
That would be nice, if it could accomodate the unusual sanlock helper requirements.