From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: what is our answer to ZFS?
Date: Mon, 21 Nov 2005 12:46:54 +0100 [thread overview]
Message-ID: <20051121114654.GA25180@merlin.emma.line.org> (raw)
In-Reply-To: <20051121101959.GB13927@wohnheim.fh-wedel.de>
On Mon, 21 Nov 2005, Jörn Engel wrote:
> o Checksums for data blocks
> Done by jffs2, not done my any hard disk filesystems I'm aware of.
Then allow me to point you to the Amiga file systems. The variants
commonly dubbed "Old File System" use only 448 (IIRC) out of 512 bytes
in a data block for payload and put their block chaining information,
checksum and other "interesting" things into the blocks. This helps
recoverability a lot but kills performance, so many people (used to) use
the "Fast File System" that uses the full 512 bytes for data blocks.
Whether the Amiga FFS, even with multi-user and directory index updates,
has a lot of importance today, is a different question that you didn't
pose :-)
> yet. (I barely consider reiser4 to exist. Any filesystem that is
> not considered good enough for kernel inclusion is effectively still
> in development phase.)
What the heck is reiserfs? I faintly recall some weirdo crap that broke
NFS throughout the better parts of 2.2 and 2.4, would slowly write junk
into its structures that reiserfsck could only fix months later.
ReiserFS 3.6 still doesn't work right (you cannot create an arbitrary
amount of arbitrary filenames in any one directory even if there's
sufficient space), after a while in production, still random flaws in
the file systems that then require rebuild-tree that works only halfway.
No thanks.
Why would ReiserFS 4 be any different? IMO reiserfs4 should be blocked
from kernel baseline until:
- reiserfs 3.6 is fully fixed up
- reiserfs 4 has been debugged in production outside the kernel for at
least 24 months with a reasonable installed base, by for instance a
large distro using it for the root fs
- there are guarantees that reiserfs 4 will be maintained until the EOL
of the kernel branch it is included into, rather than the current "oh
we have a new toy and don't give a shit about 3.6" behavior.
Harsh words, I know, but either version of reiserfs is totally out of
the game while I have the systems administrator hat on, and the recent
fuss between Namesys and Christoph Hellwig certainly doesn't raise my
trust in reiserfs.
--
Matthias Andree
next prev parent reply other threads:[~2005-11-21 11:47 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 9:28 Alfred Brons
2005-11-21 9:44 ` Paulo Jorge Matos
2005-11-21 9:59 ` Alfred Brons
2005-11-21 10:08 ` Bernd Petrovitsch
2005-11-21 10:16 ` Andreas Happe
2005-11-21 11:30 ` Anton Altaparmakov
2005-11-21 10:19 ` Jörn Engel
2005-11-21 11:46 ` Matthias Andree [this message]
2005-11-21 12:07 ` Kasper Sandberg
2005-11-21 13:18 ` Matthias Andree
2005-11-21 14:18 ` Kasper Sandberg
2005-11-21 14:41 ` Matthias Andree
2005-11-21 15:08 ` Kasper Sandberg
2005-11-22 8:52 ` Matthias Andree
2005-11-21 22:41 ` Bill Davidsen
2005-11-21 20:48 ` jdow
2005-11-22 11:17 ` Jörn Engel
2005-11-21 11:59 ` Diego Calleja
2005-11-22 7:51 ` Christoph Hellwig
2005-11-22 10:28 ` Jörn Engel
2005-11-22 14:50 ` Theodore Ts'o
2005-11-22 15:25 ` Jan Harkes
2005-11-22 16:17 ` Chris Adams
2005-11-22 16:55 ` Anton Altaparmakov
2005-11-22 17:18 ` Theodore Ts'o
2005-11-22 19:25 ` Anton Altaparmakov
2005-11-22 19:52 ` Theodore Ts'o
2005-11-22 20:00 ` Anton Altaparmakov
2005-11-22 23:02 ` Theodore Ts'o
2005-11-22 21:14 ` Bill Davidsen
2005-11-22 21:06 ` Bill Davidsen
2005-11-22 20:19 ` Alan Cox
2005-11-22 19:56 ` Chris Adams
2005-11-22 21:19 ` Bill Davidsen
2005-11-23 19:20 ` Generation numbers in stat was Re: what is slashdot's " Andi Kleen
2005-11-24 5:15 ` Chris Adams
2005-11-24 8:47 ` Andi Kleen
2005-11-22 16:28 ` what is our " Theodore Ts'o
2005-11-22 17:37 ` Jan Harkes
2005-11-22 16:36 ` Jeff V. Merkey
2005-11-28 12:53 ` Lars Marowsky-Bree
2005-11-29 5:04 ` Theodore Ts'o
2005-11-29 5:57 ` Willy Tarreau
2005-11-29 14:42 ` John Stoffel
2005-11-29 13:58 ` Andi Kleen
2005-11-29 16:03 ` Chris Adams
2005-11-21 11:45 ` Diego Calleja
2005-11-21 14:19 ` Tarkan Erimer
2005-11-21 18:52 ` Rob Landley
2005-11-21 19:28 ` Diego Calleja
2005-11-21 20:02 ` Bernd Petrovitsch
2005-11-22 5:42 ` Rob Landley
2005-11-22 9:25 ` Matthias Andree
2005-11-21 23:05 ` Bill Davidsen
2005-11-22 0:15 ` Bernd Eckenfels
2005-11-21 22:59 ` Jeff V. Merkey
2005-11-22 7:45 ` Christoph Hellwig
2005-11-22 9:19 ` Jeff V. Merkey
2005-11-22 16:00 ` Bill Davidsen
2005-11-22 16:09 ` Jeff V. Merkey
2005-11-22 20:16 ` Bill Davidsen
2005-11-22 16:14 ` Randy.Dunlap
2005-11-22 16:38 ` Steve Flynn
2005-11-22 7:15 ` Rob Landley
2005-11-22 8:16 ` Bernd Eckenfels
2005-11-22 0:45 ` Pavel Machek
2005-11-22 6:34 ` Rob Landley
2005-11-22 19:05 ` Pavel Machek
2005-11-22 9:20 ` Matthias Andree
2005-11-22 10:00 ` Tarkan Erimer
2005-11-22 15:46 ` Jan Dittmer
2005-11-22 16:27 ` Bill Davidsen
2005-11-21 18:17 ` Rob Landley
2005-11-24 1:52 art
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=20051121114654.GA25180@merlin.emma.line.org \
--to=matthias.andree@gmx.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
all inboxes | Powered by JetHome®