From: Shawn Rutledge <e_cloud@yahoo.com>
To: reiserfs-list@namesys.com
Subject: Re: ReiserFS on a flash device?
Date: Sat, 26 Jul 2003 17:03:01 -0700 [thread overview]
Message-ID: <20030727000301.GE894@ecloud.org> (raw)
In-Reply-To: <200307261640.13629.swsnyder@insightbb.com>
I wanted to use ReiserFS for an embedded system, but on a 32 or 64 meg CF
card, v3 takes up too much of it for a journal, so it wasn't practical.
Is there a way to make the journal much smaller, or have it grow
on-demand rather than being fixed-size? In practice the CF card won't
be written to very much (for longevity reasons), but I don't ever want
an embedded system to waste time fscking itself and prompting what to
do about any errors; and at the same time don't see why it should be
required to be a read-only filesystem, as is often done, because it makes
the occasional upgrade harder. And apparently JFFS2 is only for simple
memory-mapped FLASH chips without built-in write-balancing like CF cards
have.
I use the mainstream ReiserFS in Linus' kernels on all my home machines
and love it. It's so fast and stable as a rock, and the only problems
I've had were hardware-related.
On Sat, Jul 26, 2003 at 04:40:13PM -0700, Steve Snyder wrote:
> I was taken aback by Yury Umanets' recent suggestion
> (http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&safe=off&th=d50aa0bf6c7f26d0&seekm=1059231274.28094.40.camel%40haron.namesys.com.lucky.linux.kernel#link11)
> that ReiserFS is not an appropriate for a flash device.
>
> I am currently using it (via Linux kernel v2.4.21) on an E-Disk
> (http://www.bitmicro.com/products_edisk_35_scsiw.php) flash device as the
> front-end of a low-traffic Squid Web cache. The Squid experts recommend
> the use of ReiserFS (with the notail option) for it's superior
> performance in handling lots of small files. I understand that flash has
> a finite number of write cycles, but for this application performance is
> critical, and disk I/O (access times, not STR) is the bottleneck in Squid
> performance.
>
> A quote from the post referred to above:
>
> >But, if you are still want to use reiserfs for flash device, you should
> >do at least the following:
> >
> >(1) Make the journal substantial smaller of size.
> >(2) Don't turn tails off. This is useful to prolong flash live.
>
> More detail, please? How is journal size a factor? How does notails
> reduce flash longevity?
>
> Thanks.
>
>
--
_______ Shawn T. Rutledge
(_ | |_) e_cloud@yahoo.com * http://ecloud.org:8080
__) | | \________________________________________________________________
next prev parent reply other threads:[~2003-07-27 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 23:40 ReiserFS on a flash device? Steve Snyder
2003-07-27 0:03 ` Shawn Rutledge [this message]
2003-07-27 11:03 ` Yury Umanets
2003-07-27 10:55 ` Yury Umanets
2003-07-28 2:33 ` Mike Fedyk
2003-07-28 4:53 ` Yury Umanets
2003-07-28 7:05 ` Shawn Rutledge
2003-07-28 7:31 ` Yury Umanets
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=20030727000301.GE894@ecloud.org \
--to=e_cloud@yahoo.com \
--cc=reiserfs-list@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 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.