From: NeilBrown <neilb@suse.de>
To: Matthijs Kooijman <matthijs@stdin.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: MD Raid1 hangs system on read error (3.10)
Date: Mon, 6 Oct 2014 11:08:33 +1100 [thread overview]
Message-ID: <20141006110833.5028706c@notabene.brown> (raw)
In-Reply-To: <20141005092700.GA1452@login.tika.stderr.nl>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Sun, 5 Oct 2014 11:27:01 +0200 Matthijs Kooijman <matthijs@stdin.nl> wrote:
> Hey folks,
>
> a few times now I've found my system being locked up after a read error
> from a hard disk. It looks like the MD code that handles the read error
> messes up and causes a GPF.
>
> After this happens, the system becomes completely unresponsive - it
> responds to ping and opens TCP connections, but no data comes out. The
> serial console also gives no response.
>
> After rebooting, the disk in question showed a pending sector. In the
> most recent occurence, I found that the array was also resyncing. I'm
> not sure if this also happened in the earlier occurences (but since the
> pending sector didn't disappear in the next day, I'd expect no resync
> happened before). The read errors always happened during a routine check
> of the array.
That last sentence is the clue I needed - thanks.
You are running 3.10.3. It contains a bug that was fixed in 3.10.32.
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9f2d289933e60ec726a7a9522e2dcdfdc82c58de
So if you upgrade your kernel, the problem should be gone.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-10-06 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 9:27 MD Raid1 hangs system on read error (3.10) Matthijs Kooijman
2014-10-06 0:08 ` NeilBrown [this message]
2014-10-06 5:32 ` Matthijs Kooijman
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=20141006110833.5028706c@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=matthijs@stdin.nl \
/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