From: Eric Sandeen <sandeen@redhat.com>
To: Wang Shilong <wangshilong1991@gmail.com>,
Dave Stevens <geek@uniserve.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: should I use btrfs on Centos 7 for a new production server?
Date: Wed, 31 Dec 2014 00:04:08 -0600 [thread overview]
Message-ID: <54A391D8.6020201@redhat.com> (raw)
In-Reply-To: <D5E9E585-E843-4D79-A881-EB5863FB4F8B@gmail.com>
On 12/30/14 10:06 PM, Wang Shilong wrote:
>
>>
>> Hello,
>>
>>>
>>> I have a well tested and working fine Centos5-Xen system. Accumulated cruft from various development efforts make it desirable to redo the install. Currently a RAID-10 ext4 filesystem with LVM and 750G of storage. There's a hot spare 750 drive in the system.
>>>
>>> I'm thinking of migrating the web sites (almost the only use of the server) to a spare then installing Centos-7 and btrfs, then migrating the sites back.
>>>
>>> I see RH marks btrfs in C7 as a technology preview but don't understand what that implies for future support and a suitably stable basis for storage.
>>>
>>> The demand on the system is low and not likely to change in the near future, storage access speeds are not likely to be dealbreakers and it would be nice to not need to use LVM, btrfs seems to have a better feature set and more intuitive command set. But I'm uncertain about stability. Anyone have an opinion?
>>>
>>
>> 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
-Eric
next prev parent reply other threads:[~2014-12-31 6:04 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 [this message]
2014-12-31 6:16 ` Fajar A. Nugraha
2014-12-31 16:28 ` Duncan
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=54A391D8.6020201@redhat.com \
--to=sandeen@redhat.com \
--cc=geek@uniserve.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangshilong1991@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 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.