From mboxrd@z Thu Jan 1 00:00:00 1970 References: From: Zdenek Kabelac Message-ID: <5a7c3e08-2bc7-62b3-bfbf-93cc0c706ce8@redhat.com> Date: Tue, 15 Sep 2020 20:46:09 +0200 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [linux-lvm] Issue after upgrading the LVM2 package from 2.02.176 to 2.02.180 Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LVM general discussion and development , Roger Heflin 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: >> Hi 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. Regards Zdenek