From: johnrobertbanks@fastmail.fm
To: "Willy Tarreau" <w@1wt.eu>
Cc: "Jan Harkes" <jaharkes@cs.cmu.edu>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Reiser4. BEST FILESYSTEM EVER.
Date: Sat, 07 Apr 2007 06:47:03 -0700 [thread overview]
Message-ID: <1175953623.20331.1183464796@webmail.messagingengine.com> (raw)
In-Reply-To: <20070407071535.GD943@1wt.eu>
Hi Willy,...
> With decent CPU, you can reach higher read/write data rates than what a
> single off-the-shelf disk can achieve. For this reason, I think that
> reiser4 would be worth trying for this particular usage.
Glad to see you are willing to give Reiser4 a go.
Good man.
----------------------------------------------------------------------
On Sat, 7 Apr 2007 09:15:35 +0200, "Willy Tarreau" <w@1wt.eu> said:
> On Fri, Apr 06, 2007 at 10:58:45PM -0700, johnrobertbanks@fastmail.fm
> wrote:
> > You know,... you cut out this bit:
> >
> > -----------------------------------------------------------------
> >
> > > The following benchmarks are from
> > >
> > > http://linuxhelp.150m.com/resources/fs-benchmarks.htm or,
> > > http://m.domaindlx.com/LinuxHelp/resources/fs-benchmarks.htm
>
> ...
>
> Hey John, please change your disk, it's scratched and you're repeating
> yourself again and again. At first I thought "Oh cool, some good news
> about reiser4", now when I see "reiserfs" in a thread, I think "oh no,
> not this boring guy who escaped from the asylum again !". I hope this
> thread will be cut shortly so that you stop doing bad publicity to
> reiserfs and its developers, because when a product is indicated as
> good by stupid people, it's really doing harm.
>
> Also, about this part :
> [Jan]
> > > But in the end everything is a tradeoff. You can save diskspace, but
> > > increase the cost of corruption.
>
> I don't 100% agree with Jan, because for some usages (temporary space),
> light compression can increase speed. For instance, when processing logs,
> I get better speed by compressing intermediate files with LZO on the fly.
>
> [John]
> > You deliberately ignored the fact that bad blocks are NOT dealt with by
> > the filesystem,... but by the operating system. Like I said: If your
> > filesystem is writing to bad blocks, then throw away your operating
> > system.
>
> But what you write here is complete crap. The filesystem relies on a
> linear block device. The operating system is responsible for doing
> read retries or reporting errors on bad blocks, but the FS and only
> the FS can decide how not to use some known defective areas, for
> instance not putting any metadata on them nor any useful data.
>
> Now if you want to stop writing stupid things again and again, take
> your bag, don't miss the bus to school, and listen to the teachers
> instead of playing games on your calculator.
>
> Willy
> PS: non need to reply either, I'll kill this thread and your address
> here.
>
--
johnrobertbanks@fastmail.fm
--
http://www.fastmail.fm - One of many happy users:
http://www.fastmail.fm/docs/quotes.html
next prev parent reply other threads:[~2007-04-07 13:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 22:42 REISER4: fix for reiser4_write_extent Ignatich
2007-04-06 0:05 ` Reiser4. BEST FILESYSTEM EVER? I need help johnrobertbanks
2007-04-06 0:23 ` H. Peter Anvin
2007-04-06 0:34 ` johnrobertbanks
2007-04-06 0:39 ` H. Peter Anvin
2007-04-06 1:34 ` Reiser4. BEST FILESYSTEM EVER johnrobertbanks
2007-04-06 3:12 ` Valdis.Kletnieks
2007-04-06 4:07 ` H. Peter Anvin
2007-04-06 4:32 ` johnrobertbanks
[not found] ` <20070406152119.GC4228@delft.aura.cs.cmu.edu>
2007-04-07 2:47 ` johnrobertbanks
2007-04-07 3:30 ` Jan Harkes
2007-04-07 5:58 ` johnrobertbanks
2007-04-07 7:15 ` Willy Tarreau
2007-04-07 13:47 ` johnrobertbanks [this message]
2007-04-07 14:11 ` Krzysztof Halasa
2007-04-07 15:07 ` johnrobertbanks
2007-04-07 16:05 ` Pekka Enberg
2007-04-07 17:10 ` Valdis.Kletnieks
2007-04-08 16:31 ` Adrian Bunk
2007-04-07 17:21 ` Valdis.Kletnieks
2007-04-08 0:41 ` Krzysztof Halasa
2007-04-07 17:39 ` Valdis.Kletnieks
2007-04-07 19:17 ` Lennart Sorensen
2007-04-08 0:44 ` johnrobertbanks
2007-04-08 1:27 ` Lennart Sorensen
2007-04-08 2:56 ` Theodore Tso
2007-04-08 4:13 ` johnrobertbanks
2007-04-08 12:48 ` Jose Celestino
2007-04-08 13:21 ` johnrobertbanks
2007-04-08 14:14 ` Willy Tarreau
2007-04-08 17:03 ` Theodore Tso
2007-04-08 18:18 ` Jeff Mahoney
2007-04-08 4:32 ` Christer Weinigel
2007-04-08 21:50 ` Reiser4. BEST FILESYSTEM EVER - Christer Weinigel johnrobertbanks
2007-04-08 22:58 ` Richard Knutsson
2007-04-09 5:14 ` johnrobertbanks
2007-04-09 7:07 ` Willy Tarreau
2007-04-09 16:10 ` Richard Knutsson
2007-04-09 18:35 ` Reiser4. BEST FILESYSTEM EVER Nate Diller
2007-04-07 1:26 ` COMPILING AND CONFIGURING A NEW KERNEL johnrobertbanks
2007-04-07 7:45 ` johnrobertbanks
2007-04-07 16:57 ` Valdis.Kletnieks
2007-04-08 1:11 ` johnrobertbanks
2007-04-07 16:42 ` Valdis.Kletnieks
2007-04-08 1:02 ` johnrobertbanks
2007-04-08 1:42 ` Lennart Sorensen
2007-04-07 12:51 ` REISER4: fix for reiser4_write_extent Laurent Riffard
2007-04-07 19:29 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2007-04-07 12:59 Reiser4. BEST FILESYSTEM EVER Dale Amon
2007-04-07 15:28 ` johnrobertbanks
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=1175953623.20331.1183464796@webmail.messagingengine.com \
--to=johnrobertbanks@fastmail.fm \
--cc=jaharkes@cs.cmu.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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