Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
According to the man-page for the mount command EXT3 filesystems are mounted with barriers disabled by default, even tough on RHEL6 barriers are enabled by default for both EXT3 and EXT4 filesystems:
# man mount
...
Mount options for ext3
...
barrier=0 / barrier=1
... The ext3 filesystem does not enable write barriers by default.
...
This sentence should be changed to:
The ext3 filesystem enables write barriers by default.
Version-Release number of selected component (if applicable):
util-linux-ng-2.17.2-12.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. man mount
2. search for barrier option for EXT3
Additional Info:
Here's what the default mount options for a EXT3 FS look on one of my RHEL6 systems:
# grep ext3 /proc/mounts
/dev/mapper/vg_cor_scs-lv_cor_scs /usr/sap/COR/SCS00 ext3 rw,relatime,errors=continue,barrier=1,data=ordered 0 0
The FS was monuted with the default options, there is no entry in /etc/fstab specifying that barriers should be enabled for this FS.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
mount(8) man page is part of the util-linux-ng package. Changing to the correct component.
Comment 8Branislav Blaškovič
2012-12-10 13:24:53 UTC
Fix verified:
# rpm -q util-linux-ng
util-linux-ng-2.17.2-12.8.el6
# man 8 mount
barrier=0 / barrier=1
This enables/disables barriers. barrier=0 disables it, barrier=1 enables it.
Write barriers enforce proper on-disk ordering of journal commits, making volatile
disk write caches safe to use, at some performance penalty. The ext3 filesystem
enables write barriers by default. Be sure to enable barriers unless your disks
are battery-backed one way or another. Otherwise you risk filesystem corruption
in case of power failure.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0517.html