Segmentation Fault on system shutdown

fbidwell · 2004-05-30 02:21:53

When I shutdown the system. (shutdown - h now).

During the shutdown sequence I see the following error messages

>>
deactivating LVM2 groups
/var/lock/lvm : mkdir failed : read_only file system
cdrom: open failed
devfs_mk_dir : invalid argument ./etc/rc.shutdown : line 75 : 874 Segmentation Fault /sbin/lvm vgchange --ignorelockingfailure -a n

Does anyone have any idea what the problem is?

I've recently did a pacman -Syu and had to back out the kdelib and kdemultimedia upgrades because of the kdeinit segfault.

I also pacmanned in xcdroast and arson.

Thanks

cactus · 2004-05-30 07:14:55

lvm is logical volume manager...are you using logical volumes?
if not, then try compiling your kernel without support for it..since you dont need it if you are not using it...

kakabaratruskia · 2004-05-30 08:08:12

I think there's a new part in rc.conf to disable lvm. Disable it there.

cactus · 2004-05-30 09:29:18

or that.
:oops:

fbidwell · 2004-05-30 18:23:25

I'm not using LVM. Do you know what to put in the rc.conf to disable it?

I used to always get the read_only file system error, but never the segmentation fault. This started happening yesterday after a pacman -Syu.

kakabaratruskia · 2004-05-30 20:15:43

You need the latest initscripts. Look at rc.conf.pacnew There's an entry for LVM it looks like this:

.............
CONSOLEFONT=
USECOLOR="yes"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

#
# Networking
#
HOSTNAME="myhost".........

fbidwell · 2004-05-31 14:52:26

I found the rc.conf.pacman new that you referred to.

The only line that seemed new was the LVM stuff, so I added it to my rc.conf and it fixed the problem. Thanks

I have another question though.

When I upgraded my initscripts, how could I have known to look for the rc.conf.pacnew on my own? I'd like to learn for when I pacman -Syu in the future.

Dusty · 2004-05-31 16:02:17

I believe that when you run pacman and it updates a config file it says "warnig <file.conf> saved as <file.conf.pacnew>"

You should check the new files in such cases to see whats changed.

Dusty

marin_linuxer · 2004-07-14 23:33:18

In response to the OP. It seems that _if_ you are _not_ activating the LVM option in rc.conf, but the rc.shutdown script LVM2() detects the /sbin/lvm command, then it attempts to run the command, anyway. The problem you had seems to be related to the fact that the LVM command, when first run, creates some devfs nodes(!?). If you've never run the command before shutdown(after devfsd has been killed), then you get that error.

I'm gonna open a bug to request the LVM()'s in rc.shutdown eval the $USELVM in rc.conf before acting.

To answer anyone else's question about how to workaround this in meantime: just run the following, once, before shutdown:

#lvm vgchange --ignorelockingfailure -a n

OR

pacman -R lvm lvm2

apeiro · 2004-07-15 18:23:37

this bug is fixed in initscripts 0.7.

Arch Linux

#1 2004-05-30 02:21:53

Segmentation Fault on system shutdown

#2 2004-05-30 07:14:55

Re: Segmentation Fault on system shutdown

#3 2004-05-30 08:08:12

Re: Segmentation Fault on system shutdown

#4 2004-05-30 09:29:18

Re: Segmentation Fault on system shutdown

#5 2004-05-30 18:23:25

Re: Segmentation Fault on system shutdown

#6 2004-05-30 20:15:43

Re: Segmentation Fault on system shutdown

#7 2004-05-31 14:52:26

Re: Segmentation Fault on system shutdown

#8 2004-05-31 16:02:17

Re: Segmentation Fault on system shutdown

#9 2004-07-14 23:33:18

Re: Segmentation Fault on system shutdown

#10 2004-07-15 18:23:37

Re: Segmentation Fault on system shutdown

Board footer