Hi dave, Thank you for your reply, unfortunately I have rebooted that host last stat :( But good news is I have saved some logs, but I don't know weather it helps since I only saved "lvmlockctl -i", "sanlock client status", sanlock.log and messages. I pasted "sanlock client status" on https://pastebin.com/M9TRKeBk "lvmlockctl -i ": https://pastebin.com/v9E1Atig Related messages and sanlock.log: "messages": https://pastebin.com/1tqtQvDS "sanlock.log": https://pastebin.com/ESA4Wz3B Thanks! Damon David Teigland <teigland@xxxxxxxxxx> 于2018年7月10日周二 上午1:19写道： > > 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/
