All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Moshe Lazarov <Moshe.Lazarov@axxana.com>
Subject: Re: [linux-lvm] add_lockspace done -19
Date: Tue, 17 Oct 2017 11:54:56 -0500	[thread overview]
Message-ID: <20171017165456.GA22423@redhat.com> (raw)
In-Reply-To: <DB6PR0902MB221318644207A1CB3E40EA74954F0@DB6PR0902MB2213.eurprd09.prod.outlook.com>

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

      reply	other threads:[~2017-10-17 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 18:30 [linux-lvm] add_lockspace done -19 Moshe Lazarov
2017-10-13 14:41 ` David Teigland
2017-10-16 18:40   ` Moshe Lazarov
2017-10-16 18:54     ` David Teigland
2017-10-16 22:07       ` Moshe Lazarov
2017-10-17 16:54         ` David Teigland [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171017165456.GA22423@redhat.com \
    --to=teigland@redhat.com \
    --cc=Moshe.Lazarov@axxana.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.