Red Hat Bugzilla – Bug 87772
halt script segfaults during forced unmounting
Last modified: 2007-04-18 12:52:41 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE 5.0; Windows 98; DigExt)
Description of problem:
The reboot/halt process reports a segfault at the /etc/init.d/halt
script line 168 when the user of an unmounted filesystem is
'kernel'. Then, the reboot/halt process hangs indefinitely. We
have no choice but resetting the machine. We believe this might
be caused from the fuser -k -m command at the line 164 of the
script because the command would have killed the 'kernel' process!?
Or, has he entered an infinite loop at the line 154-168?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Make the remaining user of an unmounted filesystem the 'kernel' process (I
don't know how to do it!).
2.Reboot or halt.
Actual Results: The reboot/halt process indefinitely hangs after reporting a
at the line 168 of the halt script.
Expected Results: That the reboot/halt process be normally executed till their
Sometimes mounted filesystem can't be unmounted because the
umount reports Device Busy and the fuser reports that
current only remaining user of the filesystem is kernel.
I don't know why and how this could happen. If the ramaining
user is the kernel, above phenomenon occurs. This shoud be
a fatal error on the part of the init script.
This sounds like mount/umount segfaulting.
Maybe one filesystem is mounted in a subdirectory of another mounted filesystem, or
maybe the filesystem is NFS exported.
I need more information on reproducing this problem - anything you can provide would be