All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Artamonow <mad_soft@inbox.ru>
To: openembedded-devel@openembedded.org
Subject: Re: [PATCH/RFC] base-files: add noatime to rootfs mount	options
Date: Sat, 4 Apr 2009 13:09:46 +0400	[thread overview]
Message-ID: <20090404090946.GA13413@rainbow> (raw)
In-Reply-To: <gqnn72$f5t$1@ger.gmane.org>

On 13:48 Sun 29 Mar     , Koen Kooi wrote:
> On 15-03-09 21:47, Dmitry Artamonow wrote:
>> In most machines' fstabs rootfs mounted with 'defaults' option.
>> This implies that atime logging is on - i.e. on every read from
>> filesystem kernel writes atime stamp to files' metadata.
>> Here in embedded world, where rootfs is usually stored on some
>> kind of flash (internal NAND/NOR, or external SD/MMC/CF card)
>> it is a real problem, because higher number of writes causes
>> flash wearing, higher system load and higher chance of filesystem
>> corruption.
>>
>> Fix it by adding noatime to rootfs mount options in fstab.
>
> Isn't 'relatime' a better option?

Maybe yes, but we need more care in this case, because relatime has
been introduced in 2.6.20 [1], and there's still can be machines using
older kernels (judging solely by looking at the recipes in recipes/linux).
I fear that we may break booting on these machines by passing
unsupported option to mount.

[1] http://kernelnewbies.org/Linux_2_6_20#head-6804816ab4f07548635032afbedd3e1f4eb3d1d7

> regards,
>
> Koen
>

-- 
Best regards,
Dmitry "MAD" Artamonow




  reply	other threads:[~2009-04-04  9:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 20:47 [PATCH/RFC] base-files: add noatime to rootfs mount options Dmitry Artamonow
2009-03-16  0:08 ` Stanislav Brabec
2009-03-29 10:39   ` Dmitry Artamonow
2009-03-16 15:43 ` Florian Boor
2009-03-29 11:48 ` Koen Kooi
2009-04-04  9:09   ` Dmitry Artamonow [this message]
2009-04-04 17:53     ` Otavio Salvador
2009-04-15 10:21       ` Dmitry Artamonow
2009-04-15 10:27         ` [PATCH] base-files: add relatime " Dmitry Artamonow
2009-04-15 11:02           ` Koen Kooi

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=20090404090946.GA13413@rainbow \
    --to=mad_soft@inbox.ru \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 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.