From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Michael Shaver <jmshaver@gmail.com>, mdraid <linux-raid@vger.kernel.org>
Subject: Re: Kernel deadlock during mdadm reshape
Date: Wed, 27 Jul 2016 17:04:59 -0700 [thread overview]
Message-ID: <1a648537-e31e-875b-642b-b68ff83a32f6@sandisk.com> (raw)
In-Reply-To: <bbcfb493-cdee-54cd-99aa-b1f9217b3b43@gmail.com>
On 07/26/2016 07:18 PM, Michael Shaver wrote:
> I am experiencing the exact same problem reported in this thread:
>
> http://www.spinics.net/lists/raid/msg52235.html
>
> Also reported here:
>
> https://forums.gentoo.org/viewtopic-t-1043706.html
>
> And here:
>
> https://bbs.archlinux.org/viewtopic.php?id=212108
>
> I have a raid5 array of 2TB disks currently stuck at 94% of a mdadm
> reshape squeal to a grow operation from 4 disks to 5. In my case, I did
> have a drive drop out of the array during the reshape.
>
> [ ... ]
> [<ffffffff811cb8dd>] truncate_inode_pages_range+0x46d/0x880
> [<ffffffff811cbd05>] truncate_inode_pages+0x15/0x20
> [ ... ]
Hello Michael,
I ran into a similar lockup while retesting the dm-mpath driver. So we
either ran into a different lockup or the lockup was not related to the
md driver. Were you using a distro kernel or a kernel you built
yourself? Anyway, was THP (transparent huge page) support enabled? If
so, can you repeat your test with THP support disabled and see whether
that makes a difference?
Thanks,
Bart.
prev parent reply other threads:[~2016-07-28 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 2:18 Kernel deadlock during mdadm reshape Michael Shaver
2016-07-28 0:04 ` Bart Van Assche [this message]
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=1a648537-e31e-875b-642b-b68ff83a32f6@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=jmshaver@gmail.com \
--cc=linux-raid@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