From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: should I use btrfs on Centos 7 for a new production server?
Date: Wed, 31 Dec 2014 16:28:17 +0000 (UTC) [thread overview]
Message-ID: <pan$b5028$e294cf67$70ec31a2$f06c9aab@cox.net> (raw)
In-Reply-To: CAG1y0seVZipbGtonxt2iFfNYO_8kzvQZgzJeYd-zJxHUCod+sQ@mail.gmail.com
Fajar A. Nugraha posted on Wed, 31 Dec 2014 13:16:14 +0700 as excerpted:
> On Wed, Dec 31, 2014 at 1:04 PM, Eric Sandeen <sandeen@redhat.com>
> wrote:
>> On 12/30/14 10:06 PM, Wang Shilong wrote:
>>>> I used CentOS7 btrfs myself, just doing some tests..it crashed
>>>> easily.
>>>> I don’t know how much efforts that Redhat do on btrfs for 7 series.
>>>
>>> Maybe use SUSE enterprise for btrfs will be a better choice, they
>>> offered better support for btrfs as far as i know.
>>
>> I believe SuSE's most recent support statement on btrfs is here, I
>> think.
>>
>> https://www.suse.com/releasenotes/x86_64/SUSE-SLES/12/#fate-317221
>
> Wow. Suse use btrfs for root by default, but actively prevents user from
> using compression (unless specifically overiden using module parameter)?
>
> Weird, since IIRC compression has been around and stable for a long
> time.
I noticed that.
I also noticed that they mention reiserfs as btrfs-convert-ready. That I
didn't know. I thought btrfs-convert only supported ext*.
Tho I'd guess ext* has had more testing, and given the headaches I've
seen people posting here having with it, I'd strongly recommend creating
and testing a backup and restoring from it onto the new btrfs, as opposed
to doing the direct convert.
Still, I wasn't aware it was even possible, and definitely not that it
was good enough for SuSE to support. Cool that it is. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-12-31 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 3:29 should I use btrfs on Centos 7 for a new production server? Dave Stevens
2014-12-31 4:00 ` Qu Wenruo
2014-12-31 4:03 ` Wang Shilong
2014-12-31 4:06 ` Wang Shilong
2014-12-31 6:04 ` Eric Sandeen
2014-12-31 6:16 ` Fajar A. Nugraha
2014-12-31 16:28 ` Duncan [this message]
2014-12-31 18:17 ` Roman Mamedov
2014-12-31 5:55 ` Eric Sandeen
2015-01-01 8:22 ` Zygo Blaxell
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='pan$b5028$e294cf67$70ec31a2$f06c9aab@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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.