[Patch review 0/1] introduce lvm forcevg option to forcibly deactivate the whole vg

[David Teigland <teigland@redhat.com>]

> 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.)

> > 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.