lvmlockd: "lvm_global" lockspace cannot be closed normally

lvmlockd: "lvm_global" lockspace cannot be closed normally

[Eric Ren]

Hi David,

I encountered this problem pretty often when I play with lvmlockd.
"lvm_global" will stay on the system. It can be closed if using 
`dlm_tool leave lvm_global`.
But, the dlm_tool command will hang there.

It's not hard to reproduce to follow bug report [1]. Just ignore it if 
you cannot reproduce
on redhat distro, sorry I don't have time to do that currently.

[1] [lvmlockd] "lvm_global" lockspace always fails to close -
 ???? https://bugzilla.suse.com/show_bug.cgi?id=1060654

Thanks,
Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20170929/d2afca03/attachment.htm>

lvmlockd: "lvm_global" lockspace cannot be closed normally

[David Teigland]

On Fri, Sep 29, 2017 at 08:57:57PM +0800, Eric Ren wrote:
> Hi David,
> 
> I encountered this problem pretty often when I play with lvmlockd.
> "lvm_global" will stay on the system. It can be closed if using `dlm_tool
> leave lvm_global`.
> But, the dlm_tool command will hang there.

Currently the best way to handle this is to run 'lvmlockctl -S' which
stops all dlm lockspaces that lvm isn't using.  It's effectively the same
as 'vgchange --lockstop', but won't miss the global lockspace.

IIRC the vgchange issue is that stopping the global lockspace is an effect
of stopping the last VG lockspace, but sometimes vgchange finds no VGs to
stop.  I'll have another look at making vgchange --lockstop do it right.

Dave