LVM strange error

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

LVM2 is giving me some strange errors during boot, pvscan, pvdisplay, etc. I have no idea what there are... on the net, google found only one link to someone asking this, with no answer. Anyone has a clue? This is the output. Does it sound like hard drive corruption?

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

I'm pretty sure that this has something to do with LMV rather than RAID or other stuff. Does anyone know of a way to run a check or fix of an LVM partition? Or how could I know which partition is causing the trouble? Which hard drive at least? I would like to reduce the scope of the problem somehow, and so far all I know is that it has something to do with LVM.

Any ideas? :roll:

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

I've tried posting the question in the lvm official mailing list. I've registered, confirmed the registration, posted the question and it didn't even make into the list! The archives from the last 3 days don't show it!
I've also emailed the list administrator, and no answer. WTF????? :evil:

Is anyone registered into the lvm list and could post it for me? I hate mailing lists, they are just a royal PITA. I'm glad Gentoo has forums

thanks

PaveQ · Posted: Fri Feb 17, 2006 8:30 am Post subject:

I think that it isn't anything serious, just edit lvm.conf and disable something. Or compile your kernel without lvm mirroring support. I got some I/O errors too because lvm scans some non-HD devices in boot.

batistuta · Veteran Joined: 29 Jul 2005 Posts: 1384 Location: Aachen

What would you suggest dissabling? I'm not sure what could cause that...
I did compile my kernel without mirroring support, just to test that, and I still get the same problem. :roll:

I think I will anyway put it back 'cause otherwise pvmove won't work.
I don't mind so much the messages on the screen, I mind more that I don't know what this means. I would like to make sure that it's nothing wrong, but really, *nothing* comes out from google with this error. I've looked a bit a the source code where they output this message, but I can't really figure out what it does. I'm confused and this LVM guy at Red Hat is unreachable for me through the mailing list :evil:

PaveQ · Posted: Fri Feb 17, 2006 8:46 am Post subject:

I don't know... But if it works, don't fix it :roll:

chrismortimore · Posted: Fri Apr 28, 2006 2:43 am Post subject:

I only get this error with LVM2 2.02.05, which I upgraded both machines to yesterday. Before that (using LVM2 2.01.09) the error didn't appear. Did you ever find a solution for it?
_________________
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB 7200rpm Maxtor DiamondMax 10, 2x320GB WD 7200rpm Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB

MethodGuy · Tux's lil' helper Joined: 08 Apr 2005 Posts: 88

I also have this problem ...
_________________
ERROR: Keyboard not found! Press any key to continue.

zappa_the_great · Posted: Fri Apr 28, 2006 10:57 am Post subject:

Me2. I did switch back to the previous lvm2 (2.01.09) until this is resolved (looked scary...)
_________________
"I haven't lost my mind -- it's backed up on tape somewhere."

chieflilal · n00b Joined: 01 Mar 2006 Posts: 5 Location: Michigan, USA

I also am getting the same messages on boot and shutdown since upgrading to the latest version of LVM2.

I'm using then following versions on an x86
LVM2 2.02.05
Device-mapper 1.02.03

CHOST i686-pc-linux-gnu
CFLAGS -O2 -march=i686 -pipe
MAKEOPTS symlink -gtk -gnome arts X acpi alsa apm clamav cdr cups fbcon foomaticdb ghostscript hal idn joystick kde kerberos nolvmstatic nptlonly oav ogg pic ppds qt readline samba scanner theora usb vorbis win32codecs wmf xml

dmartinsca · Posted: Sat Apr 29, 2006 12:40 am Post subject:

i'm running lvm2-2.02.05 and device-mapper-1.02.05 with ~x86 with no problems. Has everyone with these errors using the same version of device-mapper as well?

chrismortimore · Posted: Sat Apr 29, 2006 6:53 am Post subject:

This morning I downgraded LVM2 to 2.01.09 and the messages went away. Perhaps 2.02.05 should get masked until this is solved? Has anyone filed a bug report?

Note: I'm using device-mapper-1.02.03 with both 2.01.09 and 2.02.05, so the problem is definitely an LVM2 issue.
_________________
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB 7200rpm Maxtor DiamondMax 10, 2x320GB WD 7200rpm Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB

chrismortimore · Posted: Sat Apr 29, 2006 6:59 am Post subject:

Opened a bug: http://bugs.gentoo.org/show_bug.cgi?id=131662
_________________
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB 7200rpm Maxtor DiamondMax 10, 2x320GB WD 7200rpm Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB 5400rpm IBM TravelStar, Nvidia 5200Go 64MB

zappa_the_great · Posted: Sat Apr 29, 2006 8:09 am Post subject:

zappa_the_great · Posted: Sun Apr 30, 2006 6:00 am Post subject:

pekster · n00b Joined: 19 Jun 2005 Posts: 16

I have had this same problem, but I believe this is related (at least partially) to the snapshot/mirror ability of LVM2. Under LVM 2.01.09 I am able to create snapshot volumes ( `lvcreate -s -L 1g -n snap vg0/test' ) but under LVM 2.02.05 it spits that "Unrecognised segment type mirror" response at me when I attempt to create a snapshot volume. I believe that the same response seen when you enter `lvm pvs' is the system complaining that it does not know how to handle these snapshot volumes (and it will generate that response even if you don't have any active snapshot volumes.)

Also, `lvm pvs' under version 2.02.05 does not list physical volumes that are created but not yet assigned to a volume group, which it does do under version 2.01.09. Is this a related problem? I can't imagine this feature was removed from the LVM code, so is this evidence of larger flaws in the code and/or ebuild?

I was eager to upgrade when a new stable version of LVM2 was released because under 2.01.09 my snapshot volumes die after about 30 seconds of extended use. However, the 2.02.05 version is a step backwards because now snapshots don't work at all and there is this new error message.

The system in question is a demo-system that our company will never be using in production use, so I would be glad to run some tests with newer masked ebuilds if this problem is addressed in one of them. Please let me know if I can run any additional tests or provide further information about my setup.

lvm 2.01.09 with device-mapper 1.02.03: creating snapshot volumes works, no errors when entering `lvm pvs'
lvm 2.02.05 with device-mapper 1.02.03: creating snapshot volumes fails, errors when entering `lvm pvs', and `lvm pvs' does not display physical volumes that are created and formatted but not assigned to a volume group

5/4/2006 Edit: corrected a typo in one of the version numbers

pekster · n00b Joined: 19 Jun 2005 Posts: 16

As a follow-up to the suggestion that LVM 2.02.05 and device-mapper 1.02.05 may solve this problem, it does not for me. I get the exact same errors as I mentioned in my post above when using device-mapper 1.02.05 and LVM 2.02.05. I do not have this problem using device-mapper 1.02.05 and LVM 2.01.09.

pekster · n00b Joined: 19 Jun 2005 Posts: 16

I poked around a bit more into this problem, and found it discussed on the redhat bugzilla database here.

It looks like this is a known problem with the device mapper kernel code that is addressed in 2.6.17-rc1 (as of this post, 2.6.17-rc3 is out.) I may try to patch the vanilla sources to 2.6.17-rc3 and copy the modified drivers/md/dm-* files into the gentoo source tree before compiling, since the 2.6.17-rc1 changes wont even make it into the gentoo-sources until its given a full version.

Itll probably be a couple days before I have a chance to do this, if I end up having time for it at all. If I do, Ill be sure to post my results here. The good news is that this problem has finally been addressed and that kernel changes will be in the next major release (2.6.17.)

pekster · n00b Joined: 19 Jun 2005 Posts: 16

I had some problems using the drivers/md/dm* files from 2.6.17-rc3 in the gentoo-sources tree, so I just recompiled my kernel to be a vanilla 2.6.17-rc3 kernel. The bad news is that this did not solve the "Unrecognised segment type mirror" message when using LVM 2.02.05 and either version of device-mapper (1.02.03 and 1.02.05.)

However, the newer kernel sources will solve problems caused by creating snapshot volumes that were broken in kernels before 2.6.17-rc1. Despite my speculation in an earlier post, these two problems seem to be unrelated (one caused by kernel drivers, the other caused by userland packages, specifically LVM2 >=2.02.05.) Snapshots still fail to create for me when using kernel 2.6.17-rc3 and LVM 2.02.05.

At this point I'm out of ideas.

pekster · n00b Joined: 19 Jun 2005 Posts: 16

Sorry for all these posts by me in a row, but I believe I may finally have the answer for our problems. The short of it is that LVM 2.02.05 is not a stable package, but is still a development one. The official sources for LVM2 are located at ftp://sources.redhat.com/pub/lvm2/ . Please note the file that reads .DEVELOPMENT_VSN_IS_2_02_05. This package should never have been unmasked in portage since the sources themselves are still in development.

Nothing above 2.01.15 should be unmasked at this time as this is the latest stable version on the release ftp site above.

chrismortimore · Posted: Fri May 12, 2006 4:18 am Post subject:

cotlod · Tux's lil' helper Joined: 08 Aug 2005 Posts: 111

I got a solution: if the use flag nomirrors don't bother you, you can put it on (emerge -pv appears with "+nomirrors") and the error message "Unrecognised segment type mirror" don't appear.

I really don't know if it is a 'good solution' but the problem seem to be solved!

PS
excuse me for my english!

I forgot: I use lvm2-2.02.05 and device-mapper-1.02.03

chrismortimore · Posted: Tue May 16, 2006 7:59 am Post subject:

bludger · Guru Joined: 09 Apr 2003 Posts: 389

The "fix" of setting the use flag of "nomirror" doesn't really sound like a fix to me, but rather a workaround.

The bug reported here: http://bugs.gentoo.org/show_bug.cgi?id=131662 is apparently fixed in lvm2 2.02.22. The latest lvm2 version on the ftp server is 2.02.24, whereas the latest version in portage is 2.02.17 (masked) and 2.02.10 (unmasked).

Is there any chance of getting this updated in portage?