From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: Yigal Sadgat <YSadgat1@gcte.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
jwboyer@linux.vnet.ibm.com, joern@logfs.org
Subject: Re: Compact Flash Question
Date: Wed, 7 May 2008 08:39:17 +0100 [thread overview]
Message-ID: <20080507083917.6eebf110@core> (raw)
In-Reply-To: <e2e108260805062315n15e84abck5f4207a6a7a11805@mail.gmail.com>
> For most Linux filesystems you really need wear leveling. E.g. ext3's
> superblock is at a fixed location and gets overwritten frequently.
> Without wear leveling you risk that the flash sector where the
> superblock resides wears out early.
CF sector mappings are not simple 1:1 mappings with flash blocks so this
is not the case. It is true with raw flash but not with CF. What CF
requires is vendor dependent but most vendors are pretty sensible.
The noatime advice is however good.
next prev parent reply other threads:[~2008-05-07 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 21:59 Compact Flash Question Yigal Sadgat
2008-05-06 22:09 ` Alan Cox
2008-05-13 17:13 ` Yigal Sadgat
2008-05-06 22:22 ` linux-os (Dick Johnson)
2008-05-07 6:15 ` Bart Van Assche
2008-05-07 7:39 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-07 7:27 Tomasz Chmielewski
[not found] <48215673.3060201@wpkg.org>
[not found] ` <e2e108260805070044v42f596bbj39c5b52b6f0a096@mail.gmail.com>
2008-05-07 7:54 ` Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche
2008-05-07 12:31 ` Helge Hafting
2008-05-07 15:01 ` Stéphane ANCELOT
2008-05-07 16:46 ` Bart Van Assche
2008-05-08 13:26 ` Mark Lord
2008-05-08 14:27 ` Lennart Sorensen
2008-05-08 14:59 ` Willy Tarreau
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=20080507083917.6eebf110@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=YSadgat1@gcte.com \
--cc=bart.vanassche@gmail.com \
--cc=joern@logfs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).