All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: "Manibalan P" <pmanibalan@amiindia.co.in>,
	"Pasi Kärkkäinen" <pasik@iki.fi>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
Date: Mon, 16 Feb 2015 17:49:57 -0500	[thread overview]
Message-ID: <wrfjd259o4iy.fsf@redhat.com> (raw)
In-Reply-To: <wrfjpp99pp9d.fsf@redhat.com> (Jes Sorensen's message of "Mon, 16 Feb 2015 15:36:46 -0500")

Jes Sorensen <Jes.Sorensen@redhat.com> writes:
> NeilBrown <neilb@suse.de> writes:
>> On Mon, 2 Feb 2015 07:10:14 +0000 Manibalan P <pmanibalan@amiindia.co.in>
>> wrote:
>>
>>> Dear All,
>>> 	Any updates on this issue.
>>
>> Probably the same as:
>>
>>   http://marc.info/?l=linux-raid&m=142283560704091&w=2
>
> Hi Neil,
>
> I ran some tests on this one against the latest Linus' tree as of today
> (1fa185ebcbcefdc5229c783450c9f0439a69f0c1) which I believe includes all
> your pending 3.20 patches.
>
> I am able to reproduce Manibalan's hangs on a system with 4 SSDs if I
> run fio on top of a device while it is resyncing and I fail one of the
> devices.

Since Manibalan mentioned this issue wasn't present in earlier kernels,
I started trying to track down what change caused it.

So far I have been able to reproduce the hang as far back as 3.10.

Cheers,
Jes

  reply	other threads:[~2015-02-16 22:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 11:06 md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization Manibalan P
2014-12-31 16:48 ` Pasi Kärkkäinen
2015-01-02  6:38   ` Manibalan P
2015-01-14 10:24   ` Manibalan P
2015-02-02  7:10   ` Manibalan P
2015-02-02 22:30     ` NeilBrown
2015-02-04  5:56       ` Manibalan P
2015-02-12 13:56       ` Manibalan P
2015-02-16 20:36       ` Jes Sorensen
2015-02-16 22:49         ` Jes Sorensen [this message]
2015-02-18  0:03           ` Jes Sorensen
2015-02-18  0:27             ` NeilBrown
2015-02-18  1:01               ` Jes Sorensen
2015-02-18  1:07                 ` Jes Sorensen
2015-02-18  1:16                   ` NeilBrown
2015-02-18  5:05                     ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2014-12-24  6:45 Manibalan P
2014-12-18  6:08 Manibalan P
2014-12-17  6:40 Manibalan P
2014-12-17  6:31 Manibalan P

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=wrfjd259o4iy.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=pasik@iki.fi \
    --cc=pmanibalan@amiindia.co.in \
    /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.