From: Bernd Eckenfels <ecki-lkm@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiser4 status: benchmarked vs. V3 (and ext3)
Date: Fri, 08 Aug 2003 16:28:34 +0200 [thread overview]
Message-ID: <E19l8EM-0006R3-00@calista.inka.de> (raw)
In-Reply-To: <1060351312.25209.468.camel@passion.cambridge.redhat.com>
In article <1060351312.25209.468.camel@passion.cambridge.redhat.com> you wrote:
> The practice of using JFFS2 on CF (and other real block devices) isn't
> really something I encourage, but it seems to have happened because
> there isn't a 'real' block device based file system which is
> powerfail-save, optimised for space and which uses compression. If
> reiser4 can fill that gap, that would be pleasing to me.
Thanks for that great article, would you care to describe where the slowness
of JFFS2 is coming from?
Do you have experiences with XFS and ext3 (datajournal) filesystems in terms
of power fail security?
Greetings
Bernd
--
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
next prev parent reply other threads:[~2003-08-08 14:28 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 21:02 Reiser4 status: benchmarked vs. V3 (and ext3) Hans Reiser
2003-07-24 4:26 ` Tupshin Harper
2003-07-24 4:31 ` Shawn
2003-07-24 4:56 ` Tupshin Harper
2003-07-24 5:21 ` Shawn
2003-07-24 5:33 ` Shawn
2003-07-24 11:10 ` Nikita Danilov
2003-07-24 15:10 ` Tupshin Harper
2003-07-24 15:26 ` Larry McVoy
2003-07-24 15:32 ` Tupshin Harper
2003-07-24 15:54 ` Larry McVoy
2003-07-24 15:32 ` Shawn
2003-07-27 12:28 ` Hans Reiser
2003-07-27 12:45 ` Tomas Szepe
2003-07-27 14:01 ` Hans Reiser
2003-07-27 15:04 ` Gene Heskett
2003-07-24 15:59 ` Daniel Egger
2003-07-24 17:07 ` Nikita Danilov
2003-07-24 21:10 ` Tupshin Harper
2003-07-25 12:57 ` Nikita Danilov
2003-07-25 0:39 ` Daniel Egger
2003-07-25 13:02 ` Nikita Danilov
2003-07-25 14:20 ` Daniel Egger
2003-07-25 14:39 ` Yury Umanets
2003-07-26 1:08 ` Daniel Egger
2003-07-26 7:19 ` Yury Umanets
2003-07-26 14:13 ` Daniel Egger
2003-07-26 14:54 ` Yury Umanets
2003-07-26 15:21 ` Daniel Egger
2003-07-27 3:28 ` Valdis.Kletnieks
2003-07-27 10:30 ` Yury Umanets
2003-07-27 11:05 ` Daniel Egger
2003-07-27 11:46 ` Yury Umanets
2003-08-08 14:01 ` David Woodhouse
2003-08-08 14:28 ` Bernd Eckenfels [this message]
2003-08-08 23:58 ` David Woodhouse
2003-08-09 0:29 ` Bernd Eckenfels
2003-08-09 0:38 ` David Woodhouse
2003-07-27 13:31 ` Hans Reiser
2003-07-27 14:13 ` Yury Umanets
2003-07-27 13:28 ` Hans Reiser
2003-07-27 14:10 ` Daniel Egger
2003-07-27 14:15 ` Yury Umanets
2003-08-13 20:12 ` Bill Davidsen
2003-08-14 5:04 ` Yury Umanets
2003-08-14 14:10 ` David Woodhouse
2003-08-15 11:15 ` Yury Umanets
2003-08-15 15:28 ` Bill Davidsen
2003-08-15 15:53 ` David Woodhouse
2003-08-14 13:58 ` David Woodhouse
2003-07-27 15:30 ` Bernd Eckenfels
2003-07-27 15:49 ` Alan Cox
2003-08-08 13:23 ` David Woodhouse
2003-07-28 11:30 ` Hans Reiser
2003-07-26 17:14 ` Jussi Laako
2003-07-27 13:35 ` Hans Reiser
2003-08-08 14:08 ` David Woodhouse
2003-07-27 12:59 ` Hans Reiser
2003-07-27 14:16 ` Daniel Egger
2003-07-27 15:32 ` Bernd Eckenfels
2003-08-08 14:29 ` David Woodhouse
2003-07-28 12:44 ` Hans Reiser
2003-07-28 13:06 ` Daniel Egger
2003-07-28 13:29 ` Hans Reiser
2003-07-28 13:48 ` Hans Reiser
2003-07-27 12:38 ` Hans Reiser
2003-07-26 8:33 ` Andrew Morton
2003-07-27 13:24 ` Hans Reiser
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=E19l8EM-0006R3-00@calista.inka.de \
--to=ecki-lkm@lina.inka.de \
--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).