All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bennett Todd <bet@rahul.net>
To: Redeeman <redeeman@metanurb.dk>
Cc: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: production use of reiserfs
Date: Mon, 1 Dec 2003 12:54:03 -0500	[thread overview]
Message-ID: <20031201175403.GC545@rahul.net> (raw)
In-Reply-To: <1070291978.4355.6.camel@redeeman.linux.dk>

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

2003-12-01T10:19:39 Redeeman:
> i feel that the linux filesystems is much more unstable after a
> power failure than windows filesystens, but in advance they are
> much faster.

In advance they're much faster because they're much more
sophisticated, with a great deal of design and implementation
focused on making them fast. Until this additional complexity is
very well debugged, they can be more fragile. ext2 is quite robust,
and I've found ext3 to be bulletproof on crashing machines.

Reiserfs is more sophisticated yet, but it has hit a quite stable
plateau; current kernel + current reiserfsprogs = very robust, with
one notable caveat: reiserfs does more critical and elaborate
computation than other filesystems, so it has acquired a reputation
for flushing hardware bugs out of the wainscotting.

If you're using reiserfs in a current prod kernel on a filesystem
built with current reiserfsprogs, and you see a crash, look for a
hardware problem. If reiserfs crashes when ext3 doesn't, look
especially hard for marginal CPU or memory that gets flaky when it's
rode hard.

> but ofcourse, windows filesystems are made to be crash proof.

If Linux crashed as often as Windows, all our filesystems would be
as robust in the face of crashes as vfat. Practice makes perfect.

-Bennett

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-12-01 17:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28  6:46 production use of reiserfs ivan
2003-11-28  9:48 ` Nikita Danilov
2003-11-28 10:42   ` ivan
2003-11-28 11:49     ` Nikita Danilov
2003-11-28  5:22       ` Hans Reiser
2003-12-01 13:33         ` Chris Mason
2003-12-01 15:26           ` Chris Mason
2003-11-28 15:20       ` Dieter Nützel
2003-12-01 15:19 ` Redeeman
2003-12-01 17:54   ` Bennett Todd [this message]

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=20031201175403.GC545@rahul.net \
    --to=bet@rahul.net \
    --cc=redeeman@metanurb.dk \
    --cc=reiserfs-list@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.