From: David Teigland <teigland@redhat.com>
To: Marc Smith <marc.smith@mcc.edu>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Error Attempting to Create LV on Clustered VG
Date: Wed, 20 Mar 2013 10:55:19 -0400 [thread overview]
Message-ID: <20130320145519.GB4759@redhat.com> (raw)
In-Reply-To: <20130320103836.58451646@jajo.eggsoft>
> > 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
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d4b0bcf32b946590afd29e202d6a399b84fe6c67
The fix is in the 3.8 kernel.
> > 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'd also advise setting up proper node definitions in corosync.conf;
it avoids the invalid nodeid issue and makes everything cleaner.
Here's what I use:
totem {
version: 2
secauth: off
cluster_name: foo
}
nodelist {
node {
ring0_addr: 1.1.1.1
nodeid: 1
}
node {
ring0_addr: 2.2.2.2
nodeid: 2
}
}
quorum {
provider: corosync_votequorum
two_node: 1
}
logging {
to_syslog: yes
}
next prev parent reply other threads:[~2013-03-20 14:55 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
2013-03-20 14:55 ` David Teigland [this message]
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=20130320145519.GB4759@redhat.com \
--to=teigland@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=marc.smith@mcc.edu \
/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).