From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm operation hangs at semop()
Date: Tue, 21 Mar 2017 19:41:03 +0000 [thread overview]
Message-ID: <20170321194103.GA15432@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAB-bdySeF5boiNRa6x16-DYPPAz75-36NwYAnK+Y3KvCz_bLBw@mail.gmail.com>
On Tue, Mar 21, 2017 at 12:07:59PM -0700, Neutron Sharc wrote:
> Is there some reference about udev rules I should use?
It should all be handled consistently by configure and make - be sure to
build and install everything in a consistent way.
If you're using a linux distribution, you'll want to build your
replacement packages using the same lvm2 configuration options / patches
that that distribution uses.
Alasdair
next prev parent reply other threads:[~2017-03-21 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:07 [linux-lvm] lvm operation hangs at semop() Neutron Sharc
2017-03-21 19:41 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-22 23:22 Neutron Sharc
2017-03-22 23:25 ` Alasdair G Kergon
2017-03-23 1:27 ` Alasdair G Kergon
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=20170321194103.GA15432@agk-dp.fab.redhat.com \
--to=agk@redhat.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 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).