Bug 50461 - non-ext2 root filesystem is not unmounted on shutdown
non-ext2 root filesystem is not unmounted on shutdown
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: 50752 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-07-31 09:41 EDT by David Nečas
Modified: 2014-03-16 22:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-31 09:42:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch (378 bytes, patch)
2001-07-31 09:41 EDT, David Nečas
no flags Details | Diff

  None (edit)
Description David Nečas 2001-07-31 09:41:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.19 i686; en-US; rv:0.9.1)

Description of problem:
/etc/init.d/halt umounts all filesystems not matching
/(^#|proc|loopfs|autofs|^none|^\/dev\/root| \/ )/
and then it remount read-only filesystems matching /ext2/ (and ummounts
proc).  Thus when root filesystem is not ext2, it is neither unmounted
(which is ok) nor remounted read-only (which is bad).

How reproducible:

Steps to Reproduce:
1. setup system to use reiserfs (for example) root filesystem
2. run poweroff / halt / reboot


Actual Results:  Root file system is left mounted read-write on shutdown,
journal log replay starts on next boot.

Expected Results:  Root file system is remounted read-only on shutdown.

Additional info:

I fixed it using the same sematics for what is excluded from unmounting and
what is then remounted read only.  Patch attached.
Comment 1 David Nečas 2001-07-31 09:41:57 EDT
Created attachment 25592 [details]
Comment 2 Bill Nottingham 2001-07-31 14:29:03 EDT
Will be fixed in 6.11-1; thanks for the patch!
Comment 3 Bill Nottingham 2001-08-02 22:46:32 EDT
*** Bug 50752 has been marked as a duplicate of this bug. ***

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