[linux-lvm] add_lockspace done -19
David Teigland
teigland at redhat.com
Tue Oct 17 16:54:56 UTC 2017
It looks like you have a permission problem. The sanlock daemon needs to
be able to use /dev/mapper/global-lvmlockd, but in your case it is getting
an EACCES error when it tries to use that device.
Check what UID/GID the sanlock daemon is running as, and that this GID is
allowed to access disks. The sanlock daemon by default will try to run
with UID/GID of sanlock/sanlock. I have things set up like this to allow
that (the sanlock rpm will typically set this up for you):
$ cat /etc/passwd | grep sanlock
sanlock:x:179:179:sanlock:/var/run/sanlock:/sbin/nologin
$ cat /etc/group | grep sanlock
disk:x:6:sanlock
tape:x:33:sanlock
sanlock:x:179:
You could also configure sanlock to run as root and not bother with the
user/group setup. Set "uname = root" and "gname = root" in
/etc/sanlock/sanlock.conf.
Dave
More information about the linux-lvm
mailing list