Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10194 - lvm2 produces warnings during boot/init process

Attached to Project: Arch Linux
Opened by Jan Spakula (bender02) - Monday, 14 April 2008, 22:26 GMT
Last edited by Greg (dolby) - Wednesday, 14 May 2008, 13:57 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
My /dev/sda4 is under LVM management. Since the update 2.02-33 -> 2.20.34. During the boot process, I see 8 times this line (4 times before 'Activating LVM groups' and 4 times after, before setting up the encrypted volumes):

Device '/dev/sda4' has been left open.

Everything after that works as usual. I haven't been able to produce these messages after the boot (by trying various lvm commands: pvdisplay, lvdisplay, vgdisplay, pvck, lvck).

Additional info:
testing/lvm2 2.02.34-1

Steps to reproduce:
Reboot.
This task depends upon

Closed by  Greg (dolby)
Wednesday, 14 May 2008, 13:57 GMT
Reason for closing:  Fixed
Comment by Jan Spakula (bender02) - Tuesday, 15 April 2008, 01:58 GMT
Sorry, first 4 are *after* 'activating lvm' and 4 are *after* encrypted volumes.
Comment by Eric Belanger (Snowman) - Thursday, 24 April 2008, 06:16 GMT
I am experiencing the same. With 2.02.33, several "Device '/dev/md2' has been left open" message appears while the kernel is booting (i.e. setting the lvm group). With 34 or 35, these messages appears after the "Activating LVM2 Group" message in the initscripts (I haven't checked if the kernal messages are still there). System boots and works fine as far as I can see. I'm using x86_64 too.
Comment by Thomas Bächler (brain0) - Thursday, 24 April 2008, 08:20 GMT
I see this on both architectures. I assume this is because I have my root device on the lvm, and thus vgchange -an at shutdown fails - I am however unsure if that is the meaning of the warning. I've been seeing this problem for a while now, but cannot see any problem in functionality. I am using lvm on one i686 and one x86_64 machine.

You see them before and after activating encrypted volumes, because vgchange -ay is executed twice (it is possible to have an encrypted volume on a lvm lv, but it is also possible to have a lvm pv on an encrypted volume).
Comment by Jan Spakula (bender02) - Thursday, 24 April 2008, 13:36 GMT
Note that I don't have my root filesystem on LVM, so rc.shutdown should be able to 'vgchange -an' my /dev/sda4.
Comment by Eric Belanger (Snowman) - Monday, 12 May 2008, 15:53 GMT
I don't have these messages anymore with 2.02.36-1 in testing.
Comment by Jan Spakula (bender02) - Monday, 12 May 2008, 19:29 GMT
Same here - no extra messages now with 2.02.36-1.
Comment by Greg (dolby) - Tuesday, 13 May 2008, 22:03 GMT
IS this solved then?
Comment by Jan Spakula (bender02) - Tuesday, 13 May 2008, 23:21 GMT
I don't know if the problem is fixed, or just the warnings disappeared. Anyway, I think the bug can be closed.

Loading...