From: C Anthony Risinger <anthony@extof.me>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Hendrik Fabelje <hendrik@fabelje.de>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Question of stability
Date: Sat, 18 Sep 2010 19:43:59 -0500 [thread overview]
Message-ID: <-2391411343414296963@unknownmsgid> (raw)
In-Reply-To: <4391908.129.1284854134163.JavaMail.root@zimbra>
On Sep 18, 2010, at 6:55 PM, Roy Sigurd Karlsbakk <roy@karlsbakk.net>
wrote:
> ----- Original Message -----
>> On Sat, Sep 18, 2010 at 11:37 PM, Roy Sigurd Karlsbakk
>> <roy@karlsbakk.net> wrote:
>>> Hi all
>>>
>>> I've been on this list for a year or so, and I have been following
>>> progress for some more. Are there any chances of btrfs >stabilizing,
>>> as in terms of usability in production? If so, how far are we from
>>> this?
>> Hi,
>>
>> I am using btrfs as my root filesystem on my Debian squeeze machine
>> for a few month now and so far I haven't experienced any problems.
>> It seems quite stable for me. I am not using raid functions, but am
>> also very interested in the progress in raid5/6.
>
> I was more interested in large setups than a general install.
>
> Question remains, when is btrfs supposed to be stable, as in usable
> for large server setups?
Stable is a pretty subjective term; many don't even think ext4 is
stable. I've used it on my personal machine since .30-31-ish without
problems, and on a server w/raid 1 for about a year (btrfs + lxc is
niiice, for VMs) also free of problems.
However, if you've been on the list you know that some do encounter
seemingly catastrophic problems, though the list is helpful in
recovering data. So, it's really going to depends on your workload
and integrity needs. I remeber someone recently using it for
continuous build servers successfully
next prev parent reply other threads:[~2010-09-19 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 21:37 Question of stability Roy Sigurd Karlsbakk
2010-09-18 21:55 ` Hendrik Fabelje
2010-09-18 23:55 ` Roy Sigurd Karlsbakk
2010-09-19 0:43 ` C Anthony Risinger [this message]
2010-09-19 2:00 ` Roy Sigurd Karlsbakk
2010-09-19 4:50 ` C Anthony Risinger
2010-09-20 15:12 ` K. Richard Pixley
2010-09-20 15:27 ` C Anthony Risinger
2010-09-19 9:51 ` Hugo Mills
2010-09-20 1:18 ` Chris Samuel
2010-09-20 11:00 ` Lubos Kolouch
2010-09-20 11:30 ` Chris Mason
2010-09-20 12:10 ` Lubos Kolouch
2010-09-20 12:13 ` Chris Mason
2010-09-22 14:04 ` Lubos Kolouch
2010-09-22 22:50 ` Chris Mason
2010-09-20 12:21 ` Stephan von Krawczynski
2010-09-20 12:27 ` Chris Mason
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=-2391411343414296963@unknownmsgid \
--to=anthony@extof.me \
--cc=hendrik@fabelje.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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;
as well as URLs for NNTP newsgroup(s).