[SOLVED] LVM2 upgrade caused LVM partition to not be recognized
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
LVM2 upgrade caused LVM partition to not be recognized
A recent upgrade to LVM2, 2.02.179, caused a curious anomaly to my bootup sequence. My /home partition, which is mounted on /dev/slack/slack, was not being initialized. After downgrading to the previous version, 2.02.177, LVM was again being initialized. I don't know how many others have experienced this problem, if at all, but I just thought I'd share my experience.
I don't know if this is related, but it seems like it might be:
Quote:
Version 2.02.178
================
There are going to be some large changes to the lvm2 codebase
over the next year or so. Starting with this release. These
changes should be internal rather than having a big effect on
the command line. Inevitably these changes will increase the
chance of bugs, so please be on the alert.
I think that might be the root of the problem. Part of the side effects of the code change could be that the code for initializing LVM will be different. Anyway, I'm sticking with the previous version until this problem is solved.
Has your home volume been around a long time? In other words, could it still be using an old metadata version that's now been removed?
I'm using LVM for almost everything here, and so far no problems with the new version.
The LVM volume is approximately 2-3 years old, and I've never had a problem with it being detected until the latest update. So I don't know whether it has old metadata information or not.
# vgscan
Reading all physical volumes. This may take a while...
Found volume group "raid1" using metadata type lvm2
Found volume group "noraid" using metadata type lvm2
Found volume group "raid0" using metadata type lvm2
# vgscan
Reading all physical volumes. This may take a while...
Found volume group "raid1" using metadata type lvm2
Found volume group "noraid" using metadata type lvm2
Found volume group "raid0" using metadata type lvm2
Code:
# vgscan
Reading all physical volumes. This may take a while...
Found volume group "slack" using metadata type lvm2
Sat Jun 23 01:22:07 UTC 2018
a/aaa_elflibs-15.0-x86_64-2.txz: Rebuilt.
Upgraded libacl.so.1 and libattr.so.1.
Added libaio.so.1 (needed by future versions of lvm).
a/lvm2-2.02.177-x86_64-1.txz: Upgraded.
Revert to the previous working version of lvm2. Based on the comments
in the release notes for version 2.02.178, perhaps it would be prudent
to sit out the next year and a half of planned instability. I can't
recall ever _needing_ to upgrade LVM (the version number has been on
2.02.x for well over a decade)... let's avoid being beta testers as
upstream refactors everything.
Well, as Pat has seen fit to revert to the previous working version, I consider this matter closed. Thanks for all the help!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.