From: Andrew Morton <akpm@digeo.com>
To: Rob van Nieuwkerk <robn@verdi.et.tudelft.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 fs: no userspace writes == no disk writes ?
Date: Thu, 19 Sep 2002 16:04:24 -0700 [thread overview]
Message-ID: <3D8A57F8.AFC627AD@digeo.com> (raw)
In-Reply-To: 20020920003058.A4850@verdi.et.tudelft.nl
Rob van Nieuwkerk wrote:
>
> Hi all,
>
> I have a question about ext3 write activity.
>
> I am considering using an ext3 fs on a CompactFlash disk for my
> data-logging application (power can disapear anytime).
> The quantity & frequency of the data logged itself is not a
> problem at all considering flash wear.
>
> But I'm a bit worried about the kernel/ext3 doing regular writes
> by itself even when there are no userspace writes. (worries are
> partially caused by memories from long time ago about idle laptop
> doing regular writes on disk).
Should be OK - it's a matter of careful monitoring and
tuning of system activity.
There are frequently written areas of an ext3 filesystem - the
journal, the superblock. Those would wear out pretty quickly.
Increasing the commit interval to the maximum acceptable time
would reduce some of this wear and tear.
There seems to be some interest in doing this. Might be helpful
to ask on ext3-users: https://listman.redhat.com/mailman/listinfo/ext3-users
next prev parent reply other threads:[~2002-09-19 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 22:30 ext3 fs: no userspace writes == no disk writes ? Rob van Nieuwkerk
2002-09-19 23:04 ` Andrew Morton [this message]
2002-09-19 23:25 ` Alan Cox
2002-09-19 23:52 ` Rob van Nieuwkerk
2002-09-20 9:04 ` Padraig Brady
2002-09-20 9:09 ` Rob van Nieuwkerk
2002-09-20 9:15 ` Padraig Brady
2002-09-20 9:19 ` Padraig Brady
2002-09-20 9:26 ` Rob van Nieuwkerk
2002-09-20 9:23 ` Rob van Nieuwkerk
-- strict thread matches above, loose matches on Subject: below --
2002-09-20 23:31 Ricardo Galli
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=3D8A57F8.AFC627AD@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robn@verdi.et.tudelft.nl \
/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