From: Omar Sandoval <osandov@osandov.com>
To: Alexander Tomokhov <alexoundos@ya.ru>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, Chris Mason <clm@fb.com>
Subject: Re: Is it possible to have metadata-only device with no data?
Date: Mon, 6 Feb 2017 10:39:44 -0800 [thread overview]
Message-ID: <20170206183944.GA20714@vader> (raw)
In-Reply-To: <14453691486330921@web21h.yandex.ru>
On Mon, Feb 06, 2017 at 12:42:01AM +0300, Alexander Tomokhov wrote:
> Is it possible, having two drives to do raid1 for metadata but keep data on a single drive only?
Chris had a patch for doing basically this that we were testing
internally, but I don't think he ever sent it to the mailing list.
prev parent reply other threads:[~2017-02-06 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 21:42 Is it possible to have metadata-only device with no data? Alexander Tomokhov
2017-02-05 21:55 ` Hans van Kranenburg
2017-02-05 23:54 ` Roman Mamedov
2017-02-14 1:20 ` Alexander Tomokhov
2017-02-06 4:26 ` Duncan
2017-02-06 12:37 ` Austin S. Hemmelgarn
2017-02-05 22:27 ` Kai Krakow
2017-02-14 1:22 ` Alexander Tomokhov
2017-02-06 18:39 ` Omar Sandoval [this message]
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=20170206183944.GA20714@vader \
--to=osandov@osandov.com \
--cc=alexoundos@ya.ru \
--cc=clm@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).