From: johnrobertbanks@fastmail.fm
To: "Richard Knutsson" <ricknu-0@student.ltu.se>
Cc: "Christer Weinigel" <christer@weinigel.se>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
reiserfs-list@namesys.com
Subject: Re: Reiser4. BEST FILESYSTEM EVER - Christer Weinigel
Date: Sun, 08 Apr 2007 22:14:18 -0700 [thread overview]
Message-ID: <1176095658.16239.1183614988@webmail.messagingengine.com> (raw)
In-Reply-To: <461973AD.5060906@student.ltu.se>
On Mon, 09 Apr 2007 00:58:53 +0200, "Richard Knutsson"
<ricknu-0@student.ltu.se> said:
> Wow, I'm impressed. Think you got the record on how many mails you
> referenced to in a reply...
TWO actually. I guess you are easily impressed.
A simple cut and paste error.
> You have got some rude answers and you have called them back on it
Yeah, I (fairly closely) mimicked their behavior to make a point.
> + you have repeated the same statement several times, that is
> not the best way of convincing people.
I know you DON'T believe that, as you are about the tenth person to
repeat that "repeating stuff has no effect."
> I believe you picked up the "anti-Reiser religion"-phrase from previous
> rant-wars (otherwise, why does that "religion"-phrase always come up,
> and (almost) only when dealing with Reiser-fs), and yes, there has been
> some clashes caused by both sides, so please be careful when dealing
> with this matter.
NO. You people simply come across as zealots who work together, against
Reiser4.
Hence the term "anti-Reiser religion."
> Would you be willing to benchmark Reiser4 with some compressed
> binary-blob and show the time as well as the CPU-usage?
I might be. I don't really know how to set it all up.
Perhaps if you guided me through it.
> >
> > 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.
> >
> I may have missed something, but if my room-mate took my harddrive,
> screwed it open, wrote a love-letter on the disk with a pencil and then
> returned it (ok, there may be some more plausible reasons for
> corruption), is the OS really suppose to handle it?
Yeah, I can't see how the OS could read the love-letter either.
But one thing is for sure. The FS ain't responsible for reading it.
> Yes, it should not
> assign any new data to those blocks but should it not also fall into the
> file-systems domain to be able to restore some/all data?
It's a tough ask of any FS.
Microsoft's filesystem checker totally roasted all my data on an XP-box
last night.
I had used ntfsresize to reduce the partition size and had a power
outage.
Later, Windows booted, ran the filesystem checker, seemed OK.
Next time I boot, all I get is Input/Output error.
>
> Just my 2c to the pond
> Richard Knutsson
>
Addin my 2c
John.
--
johnrobertbanks@fastmail.fm
--
http://www.fastmail.fm - A no graphics, no pop-ups email service
next prev parent reply other threads:[~2007-04-09 5:14 UTC|newest]
Thread overview: 48+ 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
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 [this message]
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
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=1176095658.16239.1183614988@webmail.messagingengine.com \
--to=johnrobertbanks@fastmail.fm \
--cc=christer@weinigel.se \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=ricknu-0@student.ltu.se \
/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