archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Roger Heflin <>
Subject: Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180
Date: Tue, 15 Sep 2020 20:46:09 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 15. 09. 20 v 13:05 Roger Heflin napsal(a):
> #1:
> Device /dev/sda3 excluded by a filter.)
> Failed to execute command: pvcreate -ffy /dev/sda3
> ec=0
> excluded by filter is likely the issue, I think there was a bug were
> it allowed that pvcreate to work when it should have blocked it
> because of the filter.  It should not allow a pvcreate against
> something blocked by a filter.
> #2: Read-only locking type set. Write locks are prohibited.
> I am going to guess either / is not mounted rw, or you don't have the
> directory mounted rw that is needed to create the locks (/var/run/lvm
> usually).
> On Tue, Sep 15, 2020 at 1:42 AM KrishnaMurali Chennuboina
> <> wrote:


Please consider first to use the recent/upstream version of lvm2
(ATM either 2.02.187  or  2.03.10 or git  master/stable-2.0)

Unfortunately we can't be analyzing all the bugs from all the versions out there.

So please try to provide reproducer with versions listed above.
If you can't reproduced - then you may try to bisect to discover fixing patch.

If you need to fix a particular version on your distro,
you may need to ask your package maintainer to backport
list of patches for you.
In some case however this might be hard - aka it might be more efficient
to simply go with newer version.



      parent reply	other threads:[~2020-09-15 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 13:53 [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180 KrishnaMurali Chennuboina
2020-09-14 14:58 ` Roger Heflin
2020-09-14 15:19   ` KrishnaMurali Chennuboina
2020-09-15 11:05     ` Roger Heflin
2020-09-15 12:58       ` KrishnaMurali Chennuboina
2020-09-15 17:01         ` KrishnaMurali Chennuboina
2020-09-17 16:26           ` Roger Heflin
2020-09-15 18:46       ` Zdenek Kabelac [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:

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

  git send-email \ \ \ \ \

* 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).