linux-kernel - Re: Reiser4. BEST FILESYSTEM EVER.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070407071535.GD943@1wt.eu>
Date:	Sat, 7 Apr 2007 09:15:35 +0200
From:	Willy Tarreau <w@....eu>
To:	johnrobertbanks@...tmail.fm
Cc:	Jan Harkes <jaharkes@...cmu.edu>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: Reiser4. BEST FILESYSTEM EVER.

On Fri, Apr 06, 2007 at 10:58:45PM -0700, johnrobertbanks@...tmail.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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/