From: Anand Jain <anand.jain@oracle.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] btrfs: handle volume split brain scenario
Date: Wed, 20 Dec 2017 12:46:15 +0800 [thread overview]
Message-ID: <53f056f9-5427-3b3c-5cc7-c1627439fe61@oracle.com> (raw)
In-Reply-To: <bbdcdfd8-0ff4-060c-e1db-4725aed8154f@gmail.com>
> Suppose you have 3
> devices in a raid1 and one goes missing. The user can now, in trying to
> fix this, mount each of the two remaining devices separately (by
> accident of course), in which case you can still have a split brain
> situation.
Austin, that's not possible a N disk raid1 can still miss only one
device. Sorry if I had confused you by the hard to parse commit log.
Which I have fixed it in v2.
Thanks, Anand
next prev parent reply other threads:[~2017-12-20 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-17 13:52 [PATCH RESEND 1/2] btrfs: handle volume split brain scenario Anand Jain
2017-12-17 13:52 ` [PATCH RESEND 2/2] btrfs: handle volume split brain condition for dynamically reappearing device Anand Jain
2017-12-18 12:36 ` [PATCH RESEND 1/2] btrfs: handle volume split brain scenario Austin S. Hemmelgarn
2017-12-18 14:39 ` Anand Jain
2017-12-18 16:29 ` Austin S. Hemmelgarn
2017-12-20 4:46 ` Anand Jain [this message]
2017-12-18 12:52 ` Nikolay Borisov
2017-12-18 15:03 ` Anand Jain
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=53f056f9-5427-3b3c-5cc7-c1627439fe61@oracle.com \
--to=anand.jain@oracle.com \
--cc=ahferroin7@gmail.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 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.