[Top] [All Lists]

Re: Documenting MS_LAZYTIME

To: "Michael Kerrisk (man-pages)" <mtk.manpages@xxxxxxxxx>
Subject: Re: Documenting MS_LAZYTIME
From: Theodore Ts'o <tytso@xxxxxxx>
Date: Thu, 26 Feb 2015 08:31:13 -0500
Cc: Eric Sandeen <sandeen@xxxxxxxxxx>, Ext4 Developers List <linux-ext4@xxxxxxxxxxxxxxx>, Linux btrfs Developers List <linux-btrfs@xxxxxxxxxxxxxxx>, XFS Developers <xfs@xxxxxxxxxxx>, linux-man@xxxxxxxxxxxxxxx, Linux-Fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, Linux API <linux-api@xxxxxxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=G2otT2D/i1KJckOYzuZEYeR+qbJUIrkiPB0+7z92J40=; b=pksmJBofVw591Ch2Ijl0Xhqikkqd4lLnFuwuYba9T/zT/Hkc07H7L45EKZeddgRZ/i5ltUFSjbBqustSR/dJpYdIlhq8WvylBAw9jzVgZnnPtRRvW14r7yOJRtB798WvISAxNKD7xarpeRpDe7kCwG+aRj1K2rK2oroElZwaJK8=;
In-reply-to: <54EEDE23.6080009@xxxxxxxxx>
References: <CAHO5Pa0k7QkV_6BDjwTVxa7LV9tFyN9nGFFcSvOC6HYO08wfrw@xxxxxxxxxxxxxx> <54E7578E.4090809@xxxxxxxxxx> <20150221025636.GB7922@xxxxxxxxx> <54EEDE23.6080009@xxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
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

<Prev in Thread] Current Thread [Next in Thread>