linux-kernel - Re: Compact Flash Question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e2e108260805062315n15e84abck5f4207a6a7a11805@mail.gmail.com>
Date:	Wed, 7 May 2008 08:15:23 +0200
From:	"Bart Van Assche" <bart.vanassche@...il.com>
To:	"Yigal Sadgat" <YSadgat1@...e.com>
Cc:	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org,
	jwboyer@...ux.vnet.ibm.com, joern@...fs.org
Subject: Re: Compact Flash Question

On Tue, May 6, 2008 at 11:59 PM, Yigal Sadgat <YSadgat1@...e.com> wrote:
> (2) An engineer at SanDisk Engineering told me NOT to do wear leveling.
> The file allocation table is written very frequently back into the flash. So
> is it really safe to assume that I don't need wear leveling???

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.

When using ext3 on a CompactFlash, you can limit the number of writes
to the CompactFlash significantly by mounting the medium with
parameters like noatime,nodiratime,commit=300.

Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/