From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: production ready?
Date: Thu, 14 Oct 2010 14:50:18 +0900 (JST) [thread overview]
Message-ID: <20101014.145018.209367253.ryusuke@osrg.net> (raw)
In-Reply-To: <AANLkTikL-wSkv4uTUM_g5Cs9=k3Q8TNkWXa0KNtnutXJ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
On Wed, 13 Oct 2010 12:14:46 -0500, Dwight Schauer wrote:
> Hello NILFS2 users and developers,
>
> How stable do you consider NILFS2? Performance issues aside, I'm more
> concerned about reliability.
>
> I'm considering NILFS2 for a new server setup, as BTRFS does not
> appear to production ready yet from what I've read.
>
> So, what I'm asking is this, is NILFS2 considered production ready for servers?
>
> Sincerely,
> Dwight Schauer
NILFS2 is almost stable. We have a record of nine months operation on
in-house samba servers and a webDAV server.
However, a few crash problems are reported on this mailing list and
remain unresolved. I suspect they are caused by some sort of bug
related to "garbage collection" mechanism, which often makes trouble
on this sort of filesystems.
I think you may as well wait for resolution of these issues and test
enough if you will actually apply it for business use. NILFS2 is
still marked "experimental" in kernel as with BTRFS.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-14 5:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 17:14 production ready? Dwight Schauer
[not found] ` <AANLkTikL-wSkv4uTUM_g5Cs9=k3Q8TNkWXa0KNtnutXJ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-14 5:50 ` Ryusuke Konishi [this message]
[not found] ` <20101014.145018.209367253.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-10-14 12:25 ` Jérôme Poulin
[not found] ` <AANLkTi=hk=xSFLddi5+YOpZNPPDR7rO9Y+zF8N3+Wcdy-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-14 12:55 ` Dwight Schauer
[not found] ` <AANLkTik7tjKVBrJ_P83sitOVzeGk70AQCJF_CrwG6hYU-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-18 2:57 ` Ryusuke Konishi
-- strict thread matches above, loose matches on Subject: below --
2012-10-26 21:52 Gandalf Corvotempesta
2012-10-29 20:21 ` Dan Mick
2012-10-30 11:35 ` Gandalf Corvotempesta
2012-10-30 13:15 ` Gregory Farnum
2012-10-30 13:36 ` Gandalf Corvotempesta
2012-10-30 13:38 ` Stefan Priebe - Profihost AG
2012-10-30 13:45 ` Gregory Farnum
2012-10-30 20:32 ` Stefan Priebe
2012-10-30 13:40 ` Gregory Farnum
2012-10-30 13:57 ` Gandalf Corvotempesta
2012-10-30 14:17 ` 袁冬
2012-10-30 14:31 ` Gandalf Corvotempesta
2012-10-30 14:38 ` 袁冬
2012-10-30 14:59 ` Gandalf Corvotempesta
2012-10-30 21:06 ` Dan Mick
2012-10-30 21:17 ` Gandalf Corvotempesta
2012-10-30 21:21 ` Sage Weil
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=20101014.145018.209367253.ryusuke@osrg.net \
--to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
--cc=dschauer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.