Bug 274301

Summary: Need option relatime in mount command
Product: [Fedora] Fedora Reporter: Steven Shiau <steven>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: kzak, triage
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-11 12:51:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Steven Shiau 2007-09-02 02:58:46 UTC
Description of problem:
Need option relatime for mount command

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

How reproducible:

Steps to Reproduce:
1. Mount a diskless nfs root with busybox, the result is like: / nfs
0 0
2. use the mount from util-linux-ng, remount / by
mount -n -o remount,rw /
3. It shows the error:
Unsupported nfs mount option: relatime
Actual results:
Failed to remount / 

Expected results:
mount accepts option relatime

Additional info:
The updated util-linux 2.13-0.54 (not util-linux-ng) in Fedora 7 is backported
with mount relatime patch. Is that possible to include that in util-linux-ng ?

Comment 1 Karel Zak 2007-10-02 23:08:18 UTC
This is a /sbin/mount.nfs problem. mount(8) from util-linux-ng supports relatime
option of course. See:

$ grep relatime devel/util-linux-ng-2.13/mount/*
devel/util-linux-ng-2.13/mount/mount.8:.B relatime
devel/util-linux-ng-2.13/mount/mount.c:  { "relatime",  0, 0, MS_RELATIME },  
/* Update access times relative to
devel/util-linux-ng-2.13/mount/mount.c:  { "norelatime", 0, 1, MS_RELATIME }, /*
Update access time without regard

Reassignig to nfs-utils.

Comment 2 Bug Zapper 2008-04-04 13:44:20 UTC
Based on the date this bug was created, it appears to have been reported
during the development of Fedora 8. In order to refocus our efforts as
a project we are changing the version of this bug to '8'.

If this bug still exists in rawhide, please change the version back to
(If you're unable to change the bug's version, add a comment to the bug
and someone will change it for you.)

Thanks for your help and we apologize for the interruption.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 3 Bug Zapper 2009-06-09 22:48:39 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: