All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Snyder <swsnyder@insightbb.com>
To: ReiserFS Mailing List <reiserfs-list@namesys.com>
Subject: ReiserFS on a flash device?
Date: Sat, 26 Jul 2003 16:40:13 -0700	[thread overview]
Message-ID: <200307261640.13629.swsnyder@insightbb.com> (raw)

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.




             reply	other threads:[~2003-07-26 23:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 23:40 Steve Snyder [this message]
2003-07-27  0:03 ` ReiserFS on a flash device? Shawn Rutledge
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=200307261640.13629.swsnyder@insightbb.com \
    --to=swsnyder@insightbb.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.