From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] fix device orders consistency
Date: Wed, 31 Jan 2018 10:28:54 +0800 [thread overview]
Message-ID: <20180131022856.16791-1-anand.jain@oracle.com> (raw)
v3->v2:
rename device_sort() to device_cmp().
v1->v2:
No code change. Change log updated to include the type
of problem that this consistency would help. And
I don't see patch 2/2 in the ML. So trying to resend.
By maintaining the device order (some) consistency it makes reproducing
the missing chunk related problems more consistent. (More fixes of this
sort is coming up).
Anand Jain (2):
btrfs: fix device order consistency
btrfs: fix alloc device order consistency
fs/btrfs/volumes.c | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
--
2.7.0
next reply other threads:[~2018-01-31 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 2:28 Anand Jain [this message]
2018-01-31 2:28 ` [PATCH v3 1/2] btrfs: fix device order consistency Anand Jain
2018-01-31 2:28 ` [PATCH v3 2/2] btrfs: fix alloc " Anand Jain
2018-01-31 7:03 ` [PATCH v3 0/2] fix device orders consistency Nikolay Borisov
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=20180131022856.16791-1-anand.jain@oracle.com \
--to=anand.jain@oracle.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).