From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>, Xiao Ni <xni@redhat.com>
Subject: Re: 4.1-rc6 radi5 OOPS
Date: Wed, 10 Jun 2015 12:27:35 -0400 [thread overview]
Message-ID: <wrfjk2vbv894.fsf@carbonite.lan.trained-monkey.org> (raw)
In-Reply-To: <20150610115721.64c474fa@home.neil.brown.name> (Neil Brown's message of "Wed, 10 Jun 2015 11:57:21 +1000")
Neil Brown <neilb@suse.de> writes:
> On Wed, 10 Jun 2015 10:19:42 +1000 Neil Brown <neilb@suse.de> wrote:
>
>> So it looks like some sort of race. I have other evidence of a race
>> with the resync/reshape thread starting/stopping. If I track that
>> down it'll probably fix this issue too.
>
> I think I have found just such a race. If you request a reshape just
> as a recovery completes, you can end up with two reshapes running.
> This causes confusion :-)
>
> Can you try this patch? If I can remember how to reproduce my race
> I'll test it on that too.
>
> Thanks,
> NeilBrown
Hi Neil,
Thanks for the patch - I tried with this applied, but it still crashed
for me :( I had to mangle it manually, somehow it got modified in the
email.
Note this was a mangled RHEL kernel, but it's the same crash I see on
the upstream kernel.
[ 754.303561] md: using 128k window, over a total of 19456k.
[ 754.309706] mddev->dev_sectors: 0x9800, reshape_sectors: 0x0200 stripe_addr: fffffffffffffdff, sector_nr 0, readpos 511, writepos -513, safepos 512
[ 754.324486] ------------[ cut here ]------------
[ 754.329649] kernel BUG at drivers/md/raid5.c:5388!
Cheers,
Jes
next prev parent reply other threads:[~2015-06-10 16:27 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 [this message]
2015-06-11 6:48 ` Neil Brown
2015-06-11 7:02 ` Neil Brown
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=wrfjk2vbv894.fsf@carbonite.lan.trained-monkey.org \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--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 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.