All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Valerie Henson <val_henson@linux.intel.com>
Cc: Michael Kerrisk <mtk-manpages@gmx.net>,
	val_henson@linux.interl.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Documenting MS_RELATIME
Date: Mon, 12 Feb 2007 10:40:10 -0500	[thread overview]
Message-ID: <20070212154010.GC7617@redhat.com> (raw)
In-Reply-To: <20070212065503.GC20919@nifty>

On Sun, Feb 11, 2007 at 10:55:04PM -0800, Valerie Henson wrote:
 > On Sat, Feb 10, 2007 at 07:54:00PM -0500, Dave Jones wrote:
 > > 
 > > Whilst on the subject of RELATIME, is there any good reason why
 > > not to make this a default mount option ?
 > 
 > Ubuntu has been shipping with noatime as the default for some time
 > now, with no obvious problems (I'm running Ubuntu).  I see relatime as
 > an improvement on noatime.

The one problem with noatime is that mutt's 'new mail arrived' breaks
as you mentioned in the relatime changelog, so I'm surprised that
they turned it on by default.  With relatime fixing that however,
I'm also unaware of anything that breaks.   I'd be curious to
do a Fedora test release with relatime, but I know the answer I'll
get when I recommend we add it to our generated fstabs..

"If it's good enough, why isn't it the kernel default"

Hence my current line of questioning ;-)

		Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-02-12 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 17:56 Documenting MS_RELATIME Michael Kerrisk
2007-02-11  0:54 ` Dave Jones
2007-02-12  6:55   ` Valerie Henson
2007-02-12 15:40     ` Dave Jones [this message]
2007-02-12 17:49       ` Jan Engelhardt
2007-02-12 17:55         ` Jörn Engel
2007-02-12 19:53         ` Petri Kaukasoina
2007-02-12 19:57           ` Valerie Henson
2007-02-12 19:42       ` Valerie Henson
2007-02-12  6:53 ` Valerie Henson

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=20070212154010.GC7617@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk-manpages@gmx.net \
    --cc=val_henson@linux.intel.com \
    --cc=val_henson@linux.interl.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.