Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 87772 - halt script segfaults during forced unmounting
halt script segfaults during forced unmounting
Product: Red Hat Linux
Classification: Retired
Component: util-linux (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Elliot Lee
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2003-04-02 04:53 EST by Hiroshi Iwatani
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-20 13:38:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Hiroshi Iwatani 2003-04-02 04:53:26 EST
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):

How reproducible:

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

Additional info:

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.
Comment 1 Bill Nottingham 2003-09-03 21:21:13 EDT
This sounds like mount/umount segfaulting.
Comment 2 Elliot Lee 2003-09-05 13:59:18 EDT
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 

Note You need to log in before you can comment on or make changes to this bug.