From: Neil Brown <neilb@suse.de>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, Xiao Ni <xni@redhat.com>
Subject: Re: 4.1-rc6 radi5 OOPS
Date: Thu, 11 Jun 2015 17:02:57 +1000 [thread overview]
Message-ID: <20150611170257.7033d835@home.neil.brown.name> (raw)
In-Reply-To: <20150611164847.7cd87c13@home.neil.brown.name>
On Thu, 11 Jun 2015 16:48:47 +1000
Neil Brown <neilb@suse.de> wrote:
> Would you be able to test with the following patch? There is a chance it might
> confirm whether two sync threads are running at the same time.
I tried the patch, and was fortunate:
[ 208.626468] Register thread ffff88003cf53d00 md0_resync
[ 208.629801] Started thread ffff88003cf53d00 md0_resync
[ 208.629801] Finished thread ffff88003cf53d00
[ 208.639800] Reap thread ffff88003cf53d00
[ 208.639800] Finished thread ffff88003cf53d00 md0_resync
[ 208.643133] Register thread ffff88003cf53700 md0_resync
[ 208.643133] Reap thread (null)
[ 208.646466] Started thread ffff88003cf53700 md0_resync
[ 208.659799] Reap thread ffff88003cf53700
-HANG-
That "(null)" is a problem - that will clear MD_RECOVERY_RUNNING, but there
is a thread there.
Will keep looking.
NeilBrown
next prev parent reply other threads:[~2015-06-11 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 20:20 4.1-rc6 radi5 OOPS Jes Sorensen
2015-06-03 20:40 ` NeilBrown
2015-06-03 21:57 ` Jes Sorensen
2015-06-03 22:15 ` NeilBrown
2015-06-04 1:44 ` Jes Sorensen
2015-06-10 0:19 ` Neil Brown
2015-06-10 1:57 ` Neil Brown
2015-06-10 16:27 ` Jes Sorensen
2015-06-11 6:48 ` Neil Brown
2015-06-11 7:02 ` Neil Brown [this message]
2015-06-11 7:20 ` Neil Brown
2015-06-12 21:52 ` Jes Sorensen
2015-06-13 4:26 ` Neil Brown
2015-06-10 21:02 ` Jes Sorensen
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=20150611170257.7033d835@home.neil.brown.name \
--to=neilb@suse.de \
--cc=Jes.Sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=xni@redhat.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).