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: Thu, 23 Mar 2017 01:27:53 +0000 [thread overview]
Message-ID: <20170323012753.GC15432@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20170322232512.GB15432@agk-dp.fab.redhat.com>
On Wed, Mar 22, 2017 at 11:25:12PM +0000, Alasdair G Kergon wrote:
> As I said before, if you're using a standard distro, you must find out what
> patches and config options were used to build the installed packages and use
> the same ones when you configure your own lvm build.
I've added an upstream patch so that - once it has found its way into
the distributions - you'll be able to get quickly the configuration line
used by the build by running 'lvm version'.
Alasdair
next prev parent reply other threads:[~2017-03-23 1:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 23:22 [linux-lvm] lvm operation hangs at semop() Neutron Sharc
2017-03-22 23:25 ` Alasdair G Kergon
2017-03-23 1:27 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-21 19:07 Neutron Sharc
2017-03-21 19:41 ` 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=20170323012753.GC15432@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).