Bug 1538721

Summary: mount man page says sync option has no effect for ext4
Product: Red Hat Enterprise Linux 7 Reporter: Donald Berry <dberry>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Radka Brychtova <rskvaril>
Severity: low Docs Contact:
Priority: low    
Version: 7.6CC: rskvaril, toneata
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: util-linux-2.23.2-56.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1614852 (view as bug list) Environment:
Last Closed: 2018-10-30 10:52:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1546552, 1614852    

Description Donald Berry 2018-01-25 16:40:33 UTC
Description of problem:

[root@el7a ~]# man mount

FILESYSTEM INDEPENDENT MOUNT OPTIONS

       The  following  options  apply to any filesystem that is being mounted (but not every filesystem actually honors them - e.g., the sync option
       today has effect only for ext2, ext3, fat, vfat and ufs):

BUGS

       Some Linux filesystems don't support -o sync and -o dirsync (the ext2, ext3, fat and vfat filesystems do support synchronous  updates  (a  la
       BSD) when mounted with the sync option).

Version-Release number of selected component (if applicable):

[root@el7a ~]# which mount
/usr/bin/mount
[root@el7a ~]# rpm -qf /usr/bin/mount
util-linux-2.23.2-43.el7_4.2.x86_64
[root@el7a ~]# rpm -ql util-linux-2.23.2-43.el7_4.2.x86_64 | grep man8/mount
/usr/share/man/man8/mount.8.gz

Additional info:

Same on RHEL6, Fedora 27

https://access.redhat.com/solutions/322213 says to mount ext4 with sync option for direct I/O

Comment 1 Karel Zak 2018-01-30 10:14:44 UTC
Well, it seems ext4 is missing on some places in the man page.

Comment 7 errata-xmlrpc 2018-10-30 10:52:39 UTC
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.

https://access.redhat.com/errata/RHBA-2018:3178