From: Jean-Michel Smith <jsmith@kcco.com>
To: gentoo-dev@gentoo.org, Alexander Gretencord <arutha@gmx.de>
Subject: Re: [gentoo-dev] reiserfs
Date: Tue, 14 May 2002 10:39:19 -0500 [thread overview]
Message-ID: <200205141039.19317.jsmith@kcco.com> (raw)
In-Reply-To: <200205141707.06913.arutha@gmx.de>
On Tuesday 14 May 2002 10:07 am, Alexander Gretencord wrote:
> Well, many people have run it without problems. SuSE even ships it with
> their distribution since ages (before it got into the main kernel tree).
> Without an explanation _why_ you think it's not stable enough the statement
> is worth nothing. So ACK, this definately needs an entry.
First, an appeal to authority (Suse in this case) is a logical fallacy you
should not engage in. Just because Suse ships reiser with their distribution
doesn't make it stable or safe for production use.
In fact, a friend of mine who runs a computer consultancy, and uses Suse in
nearly all of his installations, was bitten very badly by a reiserfs bug that
resulted in near-catastrophic data loss. I say near, because he was able to
recover from backup tapes. Nevertheless it resulted in an allnighter getting
the system back up, on a more reliable ext2 filesystem, followed by several
days work as he moved other installations off of reiser and onto ext2 (his
choice, not mine ... I probably would have opted for JFS or ext3 in his
particular case).
I have personally witnessed data loss using reiser on numerous occasions ...
symptoms ranged from strange "undeletable" files that were corrupt, to entire
directory trees vanishing for no apparent reason (but the disk usage
remaining unchanged). No recovery was possible in either case (short of
reconstructing a new filesystem from scratch and restoring from backups).
In all these cases all of us had all been using reiserfs "for months with no
problems" ... and we still suffered severe data loss.
Reiserfs is NOT ready for production use, and the gentoo FAQ is both wise and
friendly for pointing that out and guiding people away from that particular
folly.
There are plenty of other, much safer filesystems to use, including XFS (if
you don't need bleeding edge experimental features, e.g. can be happy with
stock 2.4.18 kernel + xfs patches), JFS, ext3, ext2 (no journalling), and so
forth. I know people tend to get very emotionally attached to whatever
filesystem they like, but this IMHO is unwise ... one should be very agnostic
about what fs one chooses to use, rather than defending a particular choice
"to the death" as seems so common with software these days.
That having been said, there is a plethora of hard evidence as well as
anectdotal experiences to learn from, and to indicate that reiser really
isn't a safe choice to be making. This is reflected in the gentoo
installation documentation, IMHO exactly as it should be.
Jean.
next prev parent reply other threads:[~2002-05-14 15:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 14:56 [gentoo-dev] reiserfs Sean Mitchell
2002-05-14 15:07 ` Alexander Gretencord
2002-05-14 15:39 ` Jean-Michel Smith [this message]
2002-05-14 15:52 ` Mark Bainter
2002-05-14 16:21 ` Jean-Michel Smith
2002-05-14 16:30 ` Ben Lutgens
2002-05-14 17:07 ` Alexander Gretencord
2002-05-14 17:22 ` Per Wigren
2002-05-14 18:50 ` Matthew Kennedy
2002-05-14 19:09 ` Jean-Michel Smith
2002-05-14 17:49 ` Mark Bainter
2002-05-14 18:17 ` Alexander Gretencord
2002-05-14 18:32 ` Mark Bainter
2002-05-14 19:03 ` Alexander Gretencord
2002-05-14 20:39 ` Mikko Moilanen
2002-05-14 22:44 ` Bill Kenworthy
2002-05-15 0:10 ` Jean-Michel Smith
2002-05-15 0:39 ` Spider
2002-05-15 0:57 ` Jean-Michel Smith
2002-05-14 21:29 ` Spider
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 15:39 Sean Mitchell
2002-05-14 14:44 Brady Wied
2002-05-14 21:17 ` Spider
2002-05-15 8:20 ` Alexander Gretencord
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=200205141039.19317.jsmith@kcco.com \
--to=jsmith@kcco.com \
--cc=arutha@gmx.de \
--cc=gentoo-dev@gentoo.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