On Thu, Jul 05, 2018 at 05:37:57PM +0800, Damon Wang wrote: > Hi, > > Sometimes I got "VG f68643c145454594871f6f51b69bf8ba lock failed: > error -221" at vg operations, likes lvcreate, while lv operation and > i/o on disks is good. It looks like the lock was acquired but not released for some reason, so subsequent attempts to acquire it are failing. There are a couple things you could send that might narrow down what happened: - Anything from /var/log/messages (or /var/log/sanlock.log) related to that lock. - 'sanlock status' which will probably show that it's still held. > I have tried stop lock and start again, but still error -221 That was the right idea. Stop was probably ignored (because it thought the lockspace/vg was busy). I'll try some possible workarounds and send you a suggestion based on that. Dave _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
