Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 17386 - Filesystems that are remounted read-only during shutdown or reboot are not synced.
Filesystems that are remounted read-only during shutdown or reboot are not sy...
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2000-09-09 15:28 EDT by Need Real Name
Modified: 2014-03-16 22:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-09-09 15:28:53 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 Need Real Name 2000-09-09 15:28:52 EDT
Unmountings of filesystems are done by /etc/rc.d/init.d/halt during
shutdown or reboot.  Some filesystems are not unmounted but remounted
read-only, e.g., the root filesystem.  Unfortunately that does not imply
that the buffers are flushed to disc.

Suggested solution:  Put a sync-command at appropriate place in

I have never had any problem with this until I started using raid1 on the
root-filesystem so that might be crucial for this bug to actually cause

I am unable to reproduce this bug in a certain way.  However, sometimes
changes in files close to a reboot are lost.

Version:  Redhat linux 6.2, i386, initscript-5.00-1.  Other versions or
platforms have not been tested.
Comment 1 Need Real Name 2000-09-09 19:08:31 EDT
After hints from some friends I checked the source code of the kernel and
remount do sync the discs.  If there is a bug here, it is not in the

My unability to reproduce the bug makes me suspect that I have made some
mistake.  At least I don't expect someone to spend time on this until I can
produce a better bug report.  Therefore I classify this as not-a-bug.

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