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#18158 - [initscripts] do not LVM volume group and devices in /dev

Attached to Project: Arch Linux
Opened by waldek (waldek_a) - Thursday, 04 February 2010, 15:39 GMT
Last edited by Eric Belanger (Snowman) - Thursday, 04 February 2010, 19:17 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: the latest initscripts do not create /dev/VolGroup/LVol files. If somebody is referring to the logical volumes through those entries, like I did in fstab for the root device, the logical volumes will fail. In my case it rendered my pc unusable.
The problem is probably caused by removal of:

< /sbin/lvm vgscan --ignorelockingfailure --mknodes >/dev/null
< /sbin/lvm vgscan --ignorelockingfailure --mknodes >/dev/

from the /etc/rc.sysinit

Additional info:
* package version: initscripts-2010.01-1-i686.pkg.tar.gz
* config and/or log files etc.


Steps to reproduce: modify fstab and make sure you used /dev/VolGroup/LVol notation (make sure you do not forget about your root partition) and reboot the pc :-)
This task depends upon

Closed by  Eric Belanger (Snowman)
Thursday, 04 February 2010, 19:17 GMT
Reason for closing:  Not a bug
Comment by Thomas Bächler (brain0) - Thursday, 04 February 2010, 17:12 GMT
$ ls -lF /dev/artin/
insgesamt 0
lrwxrwxrwx 1 root root 7 31. Jan 13:34 arch32 -> ../dm-2
lrwxrwxrwx 1 root root 7 31. Jan 13:34 arch64 -> ../dm-1
lrwxrwxrwx 1 root root 7 31. Jan 13:34 home -> ../dm-4
lrwxrwxrwx 1 root root 7 31. Jan 13:34 swap -> ../dm-3

You most likely use an outdated udev or lvm2 package.
Comment by waldek (waldek_a) - Thursday, 04 February 2010, 17:48 GMT
no, I think I have the latest:

[waldek@wolfblade ~]$ pacman -Q udev lvm2
udev 151-2
lvm2 2.02.60-2
Comment by waldek (waldek_a) - Thursday, 04 February 2010, 17:54 GMT
It looks that that everything looks fine now. I did not check today and probably the yesterday's upgrade to udev or lvm solved the problem.

[2010-02-03 19:26] upgraded udev (146-2 -> 151-2)
[2010-02-03 19:33] upgraded lvm2 (2.02.53-1 -> 2.02.60-2)

Please close the it as invalid. I am sorry I should have checked today instead of opening the ticket relaying on my memory and old data.

Loading...