From: Tomas Szepe <szepe@pinerecords.com>
To: Erik Hensema <erik@hensema.net>
Cc: linux-kernel@vger.kernel.org, lm@bitmover.com
Subject: Re: reiserfs for bkbits.net?
Date: Thu, 12 Feb 2004 14:40:22 +0100 [thread overview]
Message-ID: <20040212134022.GC8705@louise.pinerecords.com> (raw)
In-Reply-To: <slrnc2ktre.4t9.erik@bender.home.hensema.net>
On Feb-11 2004, Wed, 18:41 +0000
Erik Hensema <erik@hensema.net> wrote:
> The FS has been stable for a while now and I currently don't see
> any reason not to use it.
During the last two years, we have deployed some 400+ linux firewall
machines, all of which use reiserfs 3.6 for all of their filesystems.
While some of these boxes live in very wild environments (attics,
cellars, under the bed, in public block-of-flats corridors, ...) and
we've seen hardware die, there have been zero filesystem problems.
I think I can say we're happy with how reiser3 has fared so far.
Sounds a bit like from your favorite marketing department,
but still I thought you might want to know.
--
Tomas Szepe <szepe@pinerecords.com>
P.S. It's also very nice to never have to fsck (that is unless
a broken driver/hardware writes random crap directly to the block
device).
next prev parent reply other threads:[~2004-02-12 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:23 reiserfs for bkbits.net? Larry McVoy
2004-02-11 16:13 ` Sander
2004-02-11 16:18 ` Nikita Danilov
2004-02-11 16:30 ` Måns Rullgård
2004-02-11 18:29 ` Bryan Whitehead
2004-02-11 18:55 ` Måns Rullgård
2004-02-11 19:19 ` Larry McVoy
2004-02-12 1:06 ` Hans Reiser
2004-02-14 5:54 ` Larry McVoy
2004-02-12 8:47 ` Mihai RUSU
2004-02-11 16:44 ` Edward Shishkin
2004-02-11 16:53 ` Mihai RUSU
2004-02-11 18:05 ` Larry McVoy
2004-02-11 18:41 ` Erik Hensema
2004-02-12 13:40 ` Tomas Szepe [this message]
2004-02-19 22:33 ` Pavel Machek
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=20040212134022.GC8705@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=erik@hensema.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox