From: Theodore Ts'o <tytso@mit.edu>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux btrfs Developers List <linux-btrfs@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>,
linux-man@vger.kernel.org,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Thu, 26 Feb 2015 08:31:13 -0500 [thread overview]
Message-ID: <20150226133113.GD11217@thunk.org> (raw)
In-Reply-To: <54EEDE23.6080009@gmail.com>
On Thu, Feb 26, 2015 at 09:49:39AM +0100, Michael Kerrisk (man-pages) wrote:
> > How about somethign like "This mount significantly reduces writes
> > needed to update the inode's timestamps, especially mtime and actime.
>
> What is "actime" in the preceding line? Should it be "ctime"?
Sorry, no, it should be "atime".
> I find the wording of there a little confusing. Is the following
> a correct rewrite:
>
> The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat(2)
> will return the correctly updated atime, but the atime updates
> will be flushed to disk only when (1) the inode needs to be
> updated for filesystem / data consistency reasons or (2) the
> inode is pushed out of memory, or (3) the filesystem is
> unmounted.)
Yes, that's correct. The only other thing I might add is that in the
case of a crash, the atime (or mtime) fields on disk might be out of
date by at most 24 hours.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Ts'o <tytso@mit.edu>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
linux-man@vger.kernel.org, Linux API <linux-api@vger.kernel.org>,
XFS Developers <xfs@oss.sgi.com>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux btrfs Developers List <linux-btrfs@vger.kernel.org>
Subject: Re: Documenting MS_LAZYTIME
Date: Thu, 26 Feb 2015 08:31:13 -0500 [thread overview]
Message-ID: <20150226133113.GD11217@thunk.org> (raw)
In-Reply-To: <54EEDE23.6080009@gmail.com>
On Thu, Feb 26, 2015 at 09:49:39AM +0100, Michael Kerrisk (man-pages) wrote:
> > How about somethign like "This mount significantly reduces writes
> > needed to update the inode's timestamps, especially mtime and actime.
>
> What is "actime" in the preceding line? Should it be "ctime"?
Sorry, no, it should be "atime".
> I find the wording of there a little confusing. Is the following
> a correct rewrite:
>
> The advantage of MS_STRICTATIME | MS_LAZYTIME is that stat(2)
> will return the correctly updated atime, but the atime updates
> will be flushed to disk only when (1) the inode needs to be
> updated for filesystem / data consistency reasons or (2) the
> inode is pushed out of memory, or (3) the filesystem is
> unmounted.)
Yes, that's correct. The only other thing I might add is that in the
case of a crash, the atime (or mtime) fields on disk might be out of
date by at most 24 hours.
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-26 13:31 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 8:50 Documenting MS_LAZYTIME Michael Kerrisk
2015-02-20 8:50 ` Michael Kerrisk
2015-02-20 8:50 ` Michael Kerrisk
[not found] ` <CAHO5Pa0k7QkV_6BDjwTVxa7LV9tFyN9nGFFcSvOC6HYO08wfrw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 12:32 ` Andreas Dilger
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 13:22 ` Michael Kerrisk (man-pages)
2015-02-20 15:49 ` Eric Sandeen
2015-02-20 15:49 ` Eric Sandeen
2015-02-20 15:49 ` Eric Sandeen
2015-02-21 2:56 ` Theodore Ts'o
2015-02-21 2:56 ` Theodore Ts'o
[not found] ` <20150221025636.GB7922-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2015-02-23 12:20 ` Austin S Hemmelgarn
2015-02-23 12:20 ` Austin S Hemmelgarn
2015-02-23 12:20 ` Austin S Hemmelgarn
[not found] ` <54EB1B19.8050808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-23 16:24 ` Eric Sandeen
2015-02-23 16:24 ` Eric Sandeen
2015-02-23 16:24 ` Eric Sandeen
2015-02-26 8:53 ` Michael Kerrisk (man-pages)
2015-02-26 8:53 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 8:49 ` Michael Kerrisk (man-pages)
2015-02-26 13:31 ` Theodore Ts'o [this message]
2015-02-26 13:31 ` Theodore Ts'o
2015-02-26 13:36 ` Michael Kerrisk (man-pages)
2015-02-26 13:36 ` Michael Kerrisk (man-pages)
2015-02-27 0:04 ` Theodore Ts'o
2015-02-27 0:04 ` Theodore Ts'o
[not found] ` <20150227000409.GC17174-AKGzg7BKzIDYtjvyW6yDsg@public.gmane.org>
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
2015-02-27 8:01 ` Michael Kerrisk (man-pages)
[not found] ` <54F02446.2050008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:08 ` Omar Sandoval
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
2015-02-27 8:36 ` Michael Kerrisk (man-pages)
[not found] ` <54F02C73.5090601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 14:18 ` Theodore Ts'o
2015-02-27 17:51 ` Darrick J. Wong
2015-02-27 17:51 ` Darrick J. Wong
[not found] ` <20150227175159.GC11031-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-03-03 7:14 ` Michael Kerrisk (man-pages)
2015-02-21 7:57 ` Michael Kerrisk (man-pages)
2015-02-21 7:57 ` Michael Kerrisk (man-pages)
2015-02-22 18:30 ` Robert White
2015-02-22 18:30 ` Robert White
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=20150226133113.GD11217@thunk.org \
--to=tytso@mit.edu \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.