public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH, resend] relatime: Let relatime update atime at least once per day
Date: Sun, 28 Dec 2008 19:59:21 +0000	[thread overview]
Message-ID: <20081228195921.GB19176@srcf.ucam.org> (raw)
In-Reply-To: <4957CDD2.9040903@tudelft.nl>

On Sun, Dec 28, 2008 at 08:04:50PM +0100, Éric Piel wrote:
> Matthew Garrett schreef:
> > Ensure relatime updates atime at least once per day
> >     
> > Allow atime to be updated once per day even with relatime. This lets
> > utilities like tmpreaper (which delete files based on last access time)
> > continue working.
> :
> Sorry, but I doubt it's a good idea. First, it breaks the simple
> semantic of relatime (mtime > atime?), mixing it with a rather arbitrary
> constant. Second, and most important, there are lots of workloads which
> will be strongly affected by this modification. For instance, running
> md5sum daily on the filesystem will cause a write for every file.

Yes. And? I can't think of a single case where something could 
absolutely depend on the current relatime semantics, so altering them to 
more usefully match the atime semantics doesn't seem likely to cause any 
trouble.

> I think that to solve the problem for your use case, it's better to use
> a different approach such as mounting separately /tmp (with the atime
> option).

The use case in this case is the significant body of currently installed 
machines that don't have /tmp on a separate filesystem. In the very 
common setup of tmpreaper being used, the current relatime semantics 
will result in undesired data loss. I think the proposed alteration 
makes the behaviour of relatime massively more useful without any 
obvious drawbacks.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2008-12-28 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-28 15:29 [PATCH, resend] relatime: Let relatime update atime at least once per day Matthew Garrett
2008-12-28 18:35 ` Jesper Juhl
2008-12-28 20:19   ` Matthew Garrett
2008-12-28 19:04 ` Éric Piel
2008-12-28 19:59   ` Matthew Garrett [this message]
2008-12-28 21:24     ` Éric Piel
2008-12-28 21:36       ` Matthew Wilcox
2008-12-28 21:38       ` Matthew Garrett
2009-01-08 12:29 ` Peter Moulder
2009-01-08 13:32   ` Matthew Garrett

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=20081228195921.GB19176@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=E.A.B.Piel@tudelft.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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