LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-21-2018, 01:32 PM   #1
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
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.
 
Old 06-21-2018, 02:01 PM   #2
fskmh
Member
 
Registered: Jun 2002
Location: South Africa
Distribution: Custom slackware64-current
Posts: 278

Rep: Reputation: 72
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.
https://github.com/lvmteam/lvm2/blob...notes/2.02.178
 
1 members found this post helpful.
Old 06-21-2018, 04:26 PM   #3
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730

Original Poster
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
Quote:
Originally Posted by fskmh View Post
I don't know if this is related, but it seems like it might be:



https://github.com/lvmteam/lvm2/blob...notes/2.02.178
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.
 
Old 06-21-2018, 04:35 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,705

Rep: Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302Reputation: 5302
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.
 
Old 06-21-2018, 06:40 PM   #5
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730

Original Poster
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
Quote:
Originally Posted by volkerdi View Post
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.
 
Old 06-21-2018, 09:23 PM   #6
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,314

Rep: Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666
Code:
# pvscan
  PV /dev/md127   VG raid1           lvm2 [457.12 GiB / 429.12 GiB free]
  PV /dev/sdc1    VG noraid          lvm2 [596.17 GiB / 336.17 GiB free]
  PV /dev/md3     VG raid0           lvm2 [298.10 GiB / 88.10 GiB free]
  Total: 3 [1.32 TiB] / in use: 3 [1.32 TiB] / in no VG: 0 [0   ]
Column 5 (starting from 1, that is) is the metadata version.

Last edited by Richard Cranium; 06-21-2018 at 09:24 PM. Reason: Programmers start from 0. :-)
 
Old 06-22-2018, 07:03 PM   #7
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730

Original Poster
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
Quote:
Originally Posted by Richard Cranium View Post
Code:
# pvscan
  PV /dev/md127   VG raid1           lvm2 [457.12 GiB / 429.12 GiB free]
  PV /dev/sdc1    VG noraid          lvm2 [596.17 GiB / 336.17 GiB free]
  PV /dev/md3     VG raid0           lvm2 [298.10 GiB / 88.10 GiB free]
  Total: 3 [1.32 TiB] / in use: 3 [1.32 TiB] / in no VG: 0 [0   ]
Column 5 (starting from 1, that is) is the metadata version.
This is the output from pvscan:

Code:
# pvscan
  PV /dev/sdc1   VG slack           lvm2 [<2.73 TiB / 0    free]
  PV /dev/sdb1   VG slack           lvm2 [<2.73 TiB / 0    free]
  PV /dev/sdd1   VG slack           lvm2 [<2.73 TiB / 0    free]
  PV /dev/sde1   VG slack           lvm2 [<3.64 TiB / 0    free]
  Total: 4 [<11.83 TiB] / in use: 4 [<11.83 TiB] / in no VG: 0 [0   ]
Every time I try to upgrade to the latest version, /dev/slack/slack fails to initialize.

So what are my options here? Is there a way to "refresh" the metadata so that it is recognized on the next boot by the latest version of lvm2?

Any help will be much appreciated!

Last edited by 1337_powerslacker; 06-22-2018 at 07:06 PM.
 
Old 06-22-2018, 09:15 PM   #8
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,314

Rep: Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666
What does
Code:
vgscan
tell you?

Code:
# 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
 
Old 06-22-2018, 09:35 PM   #9
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730

Original Poster
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
Quote:
Originally Posted by Richard Cranium View Post
What does
Code:
vgscan
tell you?

Code:
# 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
 
Old 06-22-2018, 09:42 PM   #10
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,314

Rep: Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666Reputation: 1666
I believe it is safe to say that your machine is using lvm2 metadata everywhere.

Well, I guess we can look at the logical volumes as well...

Code:
# lvscan
  ACTIVE            '/dev/raid1/rootlv' [16.00 GiB] inherit
  ACTIVE            '/dev/raid1/homelv' [4.00 GiB] inherit
  ACTIVE            '/dev/raid1/loglv' [4.00 GiB] inherit
  ACTIVE            '/dev/raid1/optlv' [4.00 GiB] inherit
  ACTIVE            '/dev/noraid/mongolv' [80.00 GiB] inherit
  ACTIVE            '/dev/noraid/tmplv' [180.00 GiB] inherit
  ACTIVE            '/dev/raid0/mongolv' [130.00 GiB] inherit
  ACTIVE            '/dev/raid0/slackrepolv' [80.00 GiB] inherit
I ass-u-me that "inherit" means the logical volume is using the metadata from the volume group, but I'm sitting on where I got that information.
 
Old 06-22-2018, 10:07 PM   #11
1337_powerslacker
Member
 
Registered: Nov 2009
Distribution: Slackware64-current
Posts: 730

Original Poster
Blog Entries: 1

Rep: Reputation: 478Reputation: 478Reputation: 478Reputation: 478Reputation: 478
Code:
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!
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
reinstall/upgrade Debian over existing LVM on LUKS partition emines Debian 1 09-05-2017 08:37 PM
RHEL 7.2 changing non lvm hard disk partition to lvm2 without reinstalling OS amjadhpc Red Hat 5 03-03-2017 04:45 PM
Ignorantly erased the wrong partition; this caused my image upgrade to fail babami Linux - Newbie 5 01-02-2013 10:22 PM
Partition no more recognized after upgrade to 13.1 syvy Slackware 4 06-05-2010 02:24 PM
saving a raid+lvm partition on upgrade mort67 Linux - Software 3 10-02-2007 10:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration