From: Roman Mamedov <rm@romanrm.net>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: should I use btrfs on Centos 7 for a new production server?
Date: Wed, 31 Dec 2014 23:17:48 +0500 [thread overview]
Message-ID: <20141231231748.5db3dcea@natsu> (raw)
In-Reply-To: <pan$b5028$e294cf67$70ec31a2$f06c9aab@cox.net>
On Wed, 31 Dec 2014 16:28:17 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:
> I also noticed that they mention reiserfs as btrfs-convert-ready. That I
> didn't know. I thought btrfs-convert only supported ext*.
This might have been a mistake, or they have their own very special fork of it.
There is no sign of any ReiserFS support in
http://git.kernel.org/cgit/linux/kernel/git/mason/btrfs-progs.git/tree/btrfs-convert.c
--
With respect,
Roman
next prev parent reply other threads:[~2014-12-31 18:17 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
2014-12-31 18:17 ` Roman Mamedov [this message]
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=20141231231748.5db3dcea@natsu \
--to=rm@romanrm.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox