From: Jacek Konieczny <jajcus@jajcus.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Error Attempting to Create LV on Clustered VG
Date: Wed, 20 Mar 2013 10:38:36 +0100 [thread overview]
Message-ID: <20130320103836.58451646@jajo.eggsoft> (raw)
In-Reply-To: <CAHkw+LfrqkbZ8GUnEfz8umL22NJHep0xTmYkQ3wb-gr3rSFNhA@mail.gmail.com>
On Tue, 19 Mar 2013 12:58:53 -0400
Marc Smith <marc.smith@mcc.edu> wrote:
> Hi,
>
> I'm attempting to create a logical volume on a clustered volume group
> in a (2) node Pacemaker + Corosync cluster (active/active). I have
> successfully created the VG and it appears available on both hosts:
>
> [root@bill ~]# vgs
> VG #PV #LV #SN Attr VSize VFree
> r0 1 0 0 wz--nc 203.24g 203.24g
>
> [root@ben ~]# vgs
> VG #PV #LV #SN Attr VSize VFree
> r0 1 0 0 wz--nc 203.24g 203.24g
>
> When I attempt to create a LV on this VG from one of the hosts, I get
> the following error message:
> [root@ben ~]# lvcreate -L 150G -n testvmfs1 r0
> Error locking on node 40e6640a: Invalid argument
> Error locking on node 31e6640a: Invalid argument
> Failed to activate new LV.
[...]
> I've Google'd around a bit but haven't found any other posts quite
> like this one. Here are the software versions I'm using on these
> hosts:
> Linux kernel: 3.7.8
> LVM2: 2.02.97
> DLM User Tools (dlm_controld): 4.0.1
> Corosync: 2.3.0
> Pacemaker: 1.1.8
Are you using a 64-bit environment. If so, then this might be the bug in the
3.7 kernel DLM driver.
http://www.redhat.com/archives/cluster-devel/2013-February/msg00060.html
And here is the patch:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d4b0bcf32b946590afd29e202d6a399b84fe6c67
Greets,
Jacek
next prev parent reply other threads:[~2013-03-20 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:58 [linux-lvm] Error Attempting to Create LV on Clustered VG Marc Smith
2013-03-20 9:38 ` Jacek Konieczny [this message]
2013-03-20 14:55 ` David Teigland
2013-03-20 18:48 ` Marc Smith
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=20130320103836.58451646@jajo.eggsoft \
--to=jajcus@jajcus.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).