From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>,
Justin Engwer <justin@mautobu.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Planning out new fs. Am I missing anything?
Date: Wed, 27 May 2020 08:22:38 +0300 [thread overview]
Message-ID: <46fa65a3-137b-3164-0998-12bb996c15ef@gmail.com> (raw)
In-Reply-To: <CAJCQCtSyJp0LiaO246NcEX-p7rk8-h1NocW4o4rJgN=B1Kwrug@mail.gmail.com>
27.05.2020 05:20, Chris Murphy пишет:
>
> single, dup, raid0, raid1 (all), raid10 are safe and stable.
Until btrfs can reliably detect and automatically handle outdated device
I would not call any multi-device profiles "safe", at least unconditionally.
next prev parent reply other threads:[~2020-05-27 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 1:13 Planning out new fs. Am I missing anything? Justin Engwer
2020-05-26 12:47 ` Neal Gompa
2020-05-27 2:20 ` Chris Murphy
2020-05-27 5:22 ` Andrei Borzenkov [this message]
2020-05-27 6:25 ` Chris Murphy
2020-05-27 16:23 ` Goffredo Baroncelli
2020-05-27 18:40 ` Chris Murphy
2020-05-27 19:51 ` Goffredo Baroncelli
2020-05-28 2:14 ` Chris Murphy
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=46fa65a3-137b-3164-0998-12bb996c15ef@gmail.com \
--to=arvidjaar@gmail.com \
--cc=justin@mautobu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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).