From: Ken Ryan <linuxryan@leesburg-geeks.org>
To: Daniel Egger <degger@fhm.edu>
Cc: Hans Reiser <reiser@namesys.com>,
Timothy Miller <miller@techsource.com>,
linux-kernel@vger.kernel.org, pla@morecom.no
Subject: Re: mode data=journal in ext3. Is it safe to use?
Date: Thu, 17 Jun 2004 15:59:05 -0400 [thread overview]
Message-ID: <40D1F809.8030405@leesburg-geeks.org> (raw)
In-Reply-To: <A5938B92-C096-11D8-AAF6-000A958E35DC@fhm.edu>
Daniel Egger wrote:
> On 17.06.2004, at 19:20, Hans Reiser wrote:
>
>> Actually, most compact flash devices DO do wear leveling, from what I
>> have heard.
>
>
> Care to mention sources? I'd be surprised if they did simply because
> it'll cost money that could be earned otherwise. Also I think you
> confuse bad block remapping with wear leveling and even the former
> I haven't experienced so far.
>
> CF disks were designed for simply the reason of having an empty disk,
> writing data onto it up to a certain level, reading it a few times
> and emptying the disk again. So except for the organizational blocks
> and "the end" of a disk which tends to get rarely hit there're a
> well distributed write utilization.
>
> Servus,
> Daniel
For example:
Just bop over to the Sandisk website, go the the OEM section, and download
the manual/datasheet for CF devices. The wearlevel command itself isn't
supported (I'm ignorant of flash on IDE, I assume it is intended to mean
full scrub-style wear levelling) but they note they roll simplified wear
levelling
into the erased page pool.
Doing that is an easy way to get part of the way there without needing a
lot of
infrastructure. And for the fill-read-empty usage model it's perfectly
fine.
ken
next prev parent reply other threads:[~2004-06-17 19:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 14:56 mode data=journal in ext3. Is it safe to use? Ken Ryan
2004-06-17 16:06 ` Timothy Miller
2004-06-17 17:20 ` Hans Reiser
2004-06-17 19:15 ` Ken Ryan
2004-06-18 6:18 ` Hans Reiser
2004-06-17 19:43 ` Daniel Egger
2004-06-17 19:59 ` Ken Ryan [this message]
2004-06-19 14:49 ` Petter Larsen
[not found] <40FB8221D224C44393B0549DDB7A5CE83E31B1@tor.lokal.lan>
2004-06-15 18:09 ` Petter Larsen
2004-06-15 18:20 ` Eugene Crosser
2004-06-17 8:36 ` Petter Larsen
2004-06-16 7:34 ` Oleg Drokin
2004-06-17 8:27 ` Petter Larsen
2004-06-17 17:09 ` Oleg Drokin
2004-06-18 9:41 ` Helge Hafting
2004-06-18 10:15 ` Oleg Drokin
2004-06-18 11:30 ` Paulo Marques
2004-06-18 12:05 ` Oleg Drokin
2004-06-19 19:16 ` Bernd Eckenfels
2004-06-16 15:49 ` Timothy Miller
2004-06-17 0:51 ` Daniel Pittman
2004-06-17 3:02 ` Tim Connors
2004-06-17 5:35 ` Hans Reiser
2004-06-17 10:08 ` Dave Jones
2004-06-17 16:55 ` Hans Reiser
2004-06-17 8:29 ` Petter Larsen
2004-06-17 19:30 ` Daniel Egger
[not found] ` <87wu26mto2.fsf@enki.rimspace.net>
2004-06-27 14:17 ` Petter Larsen
2004-06-28 0:22 ` Daniel Pittman
[not found] ` <1805.216.148.213.196.1087426691.squirrel@www.code-visions.com>
2004-06-17 11:23 ` Petter Larsen
2004-06-17 16:26 ` Andreas Dilger
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=40D1F809.8030405@leesburg-geeks.org \
--to=linuxryan@leesburg-geeks.org \
--cc=degger@fhm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=pla@morecom.no \
--cc=reiser@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox