From: Theodore Tso <tytso@mit.edu>
To: Xu CanHao <xucanhao@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why ask Sun for ZFS while we have ReiserFS4 !?
Date: Tue, 1 May 2007 12:17:07 -0400 [thread overview]
Message-ID: <20070501161707.GD26093@thunk.org> (raw)
In-Reply-To: <6ec7a4340705010617h4314045cj7f0aee42eb22292b@mail.gmail.com>
On Tue, May 01, 2007 at 09:17:14PM +0800, Xu CanHao wrote:
> Reiser4 may lack some core function, but ZFS on Solaris is as
> functional as ext3 on Linux(or even more). So compare Reiser4 with
> ZFS may be inappropriate.
Functional, but it's a new filesystem with not as much time-tested
experience in the field. Many Solaris system administrators are
electing to wait rather than immediately press it into service for
critical servers, electing to use Solaris's UFS instead. I've heard a
few problems with ZFS recovering from data corruption, but not enough
to know whether it is a general trend (not that I track that kind of
stuff). As a rule, enterprise system administrators that run PO
servers for thousands of users as a time are extremely conservative,
and for good reason.
Of course, there's a big difference between those folks and people
using ZFS for their own personal development.
- Ted
next prev parent reply other threads:[~2007-05-01 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:17 Why ask Sun for ZFS while we have ReiserFS4 !? Xu CanHao
2007-05-01 16:17 ` Theodore Tso [this message]
2007-05-01 17:04 ` Xu CanHao
-- strict thread matches above, loose matches on Subject: below --
2007-04-29 18:18 Andrew Wang
2007-04-29 19:38 ` Jan Engelhardt
2007-04-29 20:32 ` Jeff Garzik
2007-04-29 23:42 ` Theodore Tso
2007-04-30 0:33 ` Chris Adams
2007-04-30 8:59 ` Matthias Andree
2007-05-01 0:35 ` Krzysztof Halasa
2007-05-02 2:43 ` lkml777
2007-05-02 18:06 ` Jan Engelhardt
2007-05-02 4:49 ` lkml777
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=20070501161707.GD26093@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=xucanhao@gmail.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