linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 114621] /etc/fstab: impossible to disable relatime
Date: Tue, 15 Mar 2016 15:21:05 +0000	[thread overview]
Message-ID: <bug-114621-13602-FuWa5oM2kY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-114621-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=114621

Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |tytso@mit.edu
         Resolution|---                         |INVALID

--- Comment #1 from Theodore Tso <tytso@mit.edu> ---
These errors have nothing to do with relatime.  

You can control whether the last access time is updated on every single read
(which is a performance disaster, but required by POSIX) using the mount option
strictatime.  You can also set the last access time to never be updated using
the mount option noatime.   The default, relatime will update atime if it is
more than 24 hours out of date, or if atime < mtime. 

None of this has anything to do with the NCQ error, which is coming from the
device, and not the file system.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2016-03-15 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 12:17 [Bug 114621] New: /etc/fstab: impossible to disable relatime bugzilla-daemon
2016-03-15 15:21 ` bugzilla-daemon [this message]
2016-03-15 17:32 ` [Bug 114621] " bugzilla-daemon
2016-03-15 21:39 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-114621-13602-FuWa5oM2kY@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).