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.
Bug 665376 - incorrectly documented the mount "atime" option
Summary: incorrectly documented the mount "atime" option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-23 14:01 UTC by Debbie Johnson
Modified: 2018-11-14 16:38 UTC (History)
5 users (show)

Fixed In Version: util-linux-ng-2.17.2-9.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 14:06:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0699 0 normal SHIPPED_LIVE util-linux-ng bug fix and enhancement update 2011-05-18 18:10:13 UTC

Description Debbie Johnson 2010-12-23 14:01:46 UTC 
Description of problem:
The mount command with atime option always mounts filesystems as relatime.
According to mount's man page, atime option appears to work as well as
strictatime option. Please see below.

[man mount]
...
atime Update inode access time for each access. See also the strictatime
mount option.
...

As you see, the description of atime points to strictatime's. We confirmed
the behavior of strictatime is the same as RHEL5's atime. So, we suppose
atime should work as well as strictatime. We believe that this is due to a
bug of atime. Could you please fix mount so that it works properly?

Version-Release number of selected component:
Red Hat Enterprise Linux Version Number: 6
Release Number: RC1
Architecture: x86_64
Kernel Version: kernel-2.6.32-71.el6.x86_64
Related Package Version: util-linux-ng-2.17.2-6.el6.x86_64
Related Middleware / Application: N/A

Drivers or hardware or architecture dependency:
None.

How reproducible:
Always

Step to Reproduce:
1. Run mount command with atime option
# mount -o atime /dev/sdb1 /tmp/bar

2. Check the mount's option
# cat /proc/mounts
...
/dev/sdb1 /tmp/bar ext4 rw,relatime,barrier=1,data=ordered 0 0
<The filesystem should be mounted as not atime but relatime.>

Actual Results:
An option "atime" of mount doesn't work as expected.

Expected Results:
An option "atime" of mount works as well as an option strictatime.

Summary of actions taken to resolve issue:
None.

Location of diagnostic data:
None.

Hardware configuration:
Model: Fujitsu PRIMERGY RX300S4
CPU Info: Intel(R) Xeon(R) E5420 2.50GHz
Memory Info: 12GB
Hardware Component Information: None.
Configuration Info: None.
Guest Configuration Info: None.

Business Impact:

Target Release:6.2

Errata Request:No.

Hotfix Request:No.


A fix has been provided by customer which simply is a fix to man pages.. this is attached.
Comment 1 Eric Sandeen 2011-01-17 17:35:53 UTC 
It's the mount binary which handles "strictatime" and "atime" options, in util-linux-ng ...  it needs to pass MS_STRICTATIME flags to the mount syscall if that behavior is desired.  It does for strictatime but does not for atime.

Karel, is "atime" supposed to work as well?
Comment 2 Karel Zak 2011-01-18 09:53:15 UTC 
(In reply to comment #1)
> It's the mount binary which handles "strictatime" and "atime" options, in
> util-linux-ng ...  it needs to pass MS_STRICTATIME flags to the mount syscall
> if that behavior is desired.  It does for strictatime but does not for atime.
> 
> Karel, is "atime" supposed to work as well?

There is not relation between atime and strictatime in mount(8). The traditional way how mount(8) works with mount flags is:

 noatime:  flags |= MS_NOATIME
   atime:  flags &= ~MS_NOATIME

so set/unset the flag only. There is not any other logic. The rest have to be done in kernel. I don't think that mount(8) is the right place to play any game with mount flags...

The latest upstream version of the man page:

  atime  Update inode access time for each access. 
         See also the strictatime mount option.

noatime  Do  not  update inode access times on this filesystem 
         (e.g, for faster access on the news spool to 
          speed up news servers).

strictatime
         Allows to explicitly requesting full atime updates. This makes 
         it possible for kernel to  defaults to  relatime or noatime but
         still allow userspace to override it. For more details about the
         default system mount options see /proc/mounts.


The "atime" description is probably bad, should be "disable noatime option, 
the inode access time is controlled by kernel defaults, see strictatime for more details" or so...
Comment 7 errata-xmlrpc 2011-05-19 14:06:43 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0699.html
Note You need to log in before you can comment on or make changes to this bug.