From: "Hérikz Nawarro" <herikz.nawarro@gmail.com>
To: "Hugo Mills" <hugo@carfax.org.uk>,
"Hérikz Nawarro" <herikz.nawarro@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid assurance
Date: Tue, 25 Jul 2017 10:50:38 -0300 [thread overview]
Message-ID: <CAD6NJSwCPgQbd3Fw9Gam6kPMJMXt_1wgUBCZGym5tKTSoSbUFg@mail.gmail.com> (raw)
In-Reply-To: <20170725134656.GL7140@carfax.org.uk>
Thanks everyone, I'll stick with raid 1.
next prev parent reply other threads:[~2017-07-25 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 12:55 btrfs raid assurance Hérikz Nawarro
2017-07-25 13:16 ` Austin S. Hemmelgarn
2017-07-25 13:46 ` Hugo Mills
2017-07-25 13:50 ` Hérikz Nawarro [this message]
2017-07-25 13:51 ` Hugo Mills
2017-07-25 13:55 ` Hérikz Nawarro
2017-07-25 13:58 ` Hugo Mills
2017-07-25 21:29 ` waxhead
2017-07-25 21:45 ` Hugo Mills
2017-07-26 12:12 ` Austin S. Hemmelgarn
2017-07-26 12:27 ` Hugo Mills
2017-07-26 12:28 ` Hugo Mills
2017-07-26 12:36 ` Austin S. Hemmelgarn
2017-07-26 23:07 ` Hugo Mills
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=CAD6NJSwCPgQbd3Fw9Gam6kPMJMXt_1wgUBCZGym5tKTSoSbUFg@mail.gmail.com \
--to=herikz.nawarro@gmail.com \
--cc=hugo@carfax.org.uk \
--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).