From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, nate.dailey@stratus.com
Subject: [PATCH 0/1] Fix raid1 resync getting stuck
Date: Wed, 16 Sep 2015 10:20:04 -0400 [thread overview]
Message-ID: <1442413205-9593-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Neil,
This patch seems to do the job for us. Nate ran testing with > 500
iterations which would normally fail in less than 10.
I tried changing MaxSector to ((~(sector_t)0) >> 1) as you suggested,
but that made the raid5 code go explosive. This on the other hand
seems to do the trick.
Cheers,
Jes
Jes Sorensen (1):
md/raid1: Avoid raid1 resync getting stuck
drivers/md/raid1.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.4.3
next reply other threads:[~2015-09-16 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 14:20 Jes.Sorensen [this message]
2015-09-16 14:20 ` [PATCH 1/1] md/raid1: Avoid raid1 resync getting stuck Jes.Sorensen
2015-09-23 6:49 ` Neil Brown
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=1442413205-9593-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=nate.dailey@stratus.com \
--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).