From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 713EE7F47 for ; Thu, 26 Feb 2015 07:36:43 -0600 (CST) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay3.corp.sgi.com (Postfix) with ESMTP id E6359AC006 for ; Thu, 26 Feb 2015 05:36:39 -0800 (PST) Received: from mail-wg0-f48.google.com (mail-wg0-f48.google.com [74.125.82.48]) by cuda.sgi.com with ESMTP id 3xdp1BKOpbdr6Dno (version=TLSv1 cipher=RC4-SHA bits=128 verify=NO) for ; Thu, 26 Feb 2015 05:36:37 -0800 (PST) Received: by wggx12 with SMTP id x12so10761721wgg.11 for ; Thu, 26 Feb 2015 05:36:36 -0800 (PST) Message-ID: <54EF2161.90607@gmail.com> Date: Thu, 26 Feb 2015 14:36:33 +0100 From: "Michael Kerrisk (man-pages)" MIME-Version: 1.0 Subject: Re: Documenting MS_LAZYTIME References: <54E7578E.4090809@redhat.com> <20150221025636.GB7922@thunk.org> <54EEDE23.6080009@gmail.com> <20150226133113.GD11217@thunk.org> In-Reply-To: <20150226133113.GD11217@thunk.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Theodore Ts'o Cc: Eric Sandeen , linux-man@vger.kernel.org, Linux API , XFS Developers , mtk.manpages@gmail.com, Linux-Fsdevel , Ext4 Developers List , Linux btrfs Developers List On 02/26/2015 02:31 PM, Theodore Ts'o wrote: > 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". Thanks. >> 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. So in other words, add a sentence to that last para: The disadvantage of MS_STRICTATIME | MS_LAZYTIME is that in the case of a system crash, the atime and mtime fields on disk might be out of date by at most 24 hours. Right? Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs