From: Jonathan Brassow <jbrassow@redhat.com>
To: dm-devel@redhat.com, linux-raid@vger.kernel.org
Cc: agk@redhat.com, neilb@suse.de
Subject: [PATCH 0 of 4] dm-raid: various bug fixes
Date: Tue, 17 Apr 2012 21:30:19 -0500 [thread overview]
Message-ID: <1334716219.23908.14.camel@f14.redhat.com> (raw)
Neil,
I've cleaned up the first two patches I sent earlier:
[1 of 5] dm-raid-set-recovery-flags-on-resume.patch
[2 of 5] dm-raid-record-and-handle-missing-devices.patch
and added a couple more:
[3 of 5] dm-raid-need-safe-version-of-rdev_for_each.patch
[4 of 5] dm-raid-use-md_error-in-place-of-faulty-bit.patch
[5 of 5] md-raid1-further-conditionalize-fullsync.patch
Patch [5 of 5] I think needs some work. It fixes the problem I'm seeing
and seems to go along with similar logic used for RAID5 in commit
d6b212f4b19da5301e6b6eca562e5c7a2a6e8c8d. It also seems like a workable
solution based on the code surrounding commit
d30519fc59c5cc2f7772fa67b16b1a2426d36c95. Can you let me know if I'm
stretching the usage of 'saved_raid_disk' too far?
Thanks,
brassow
next reply other threads:[~2012-04-18 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 2:30 Jonathan Brassow [this message]
2012-04-18 2:36 ` [PATCH 1 of 5] DM RAID: Set recovery flags on resume Jonathan Brassow
2012-04-18 2:37 ` [PATCH 2 of 5] DM RAID: Record and handle missing devices Jonathan Brassow
2012-04-18 2:38 ` [PATCH 3 of 5] DM RAID: Use safe version of rdev_for_each Jonathan Brassow
2012-04-18 2:41 ` [PATCH 4 of 5] DM RAID: Use md_error() in place of simply setting Faulty bit Jonathan Brassow
2012-04-18 2:43 ` [PATCH 5 of 5] MD RAID1: Further conditionalize 'fullsync' Jonathan Brassow
2012-04-18 3:48 ` [PATCH 0 of 4] dm-raid: various bug fixes NeilBrown
2012-04-18 14:05 ` Brassow Jonathan
2012-04-18 21:32 ` Brassow Jonathan
2012-04-18 23:58 ` [dm-devel] " NeilBrown
2012-04-19 2:42 ` Brassow Jonathan
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=1334716219.23908.14.camel@f14.redhat.com \
--to=jbrassow@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).