From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: 'NeilBrown' <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
Date: Fri, 26 Jul 2013 05:56:51 -0400 [thread overview]
Message-ID: <001e01ce89e6$73f93b80$5bebb280$@lucidpixels.com> (raw)
In-Reply-To: <20130726103549.1e6b0b92@notabene.brown>
-----Original Message-----
From: NeilBrown [mailto:neilb@suse.de]
Sent: Thursday, July 25, 2013 8:36 PM
To: Justin Piszcz
Cc: linux-kernel@vger.kernel.org; linux-raid@vger.kernel.org
Subject: Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x
SSD)
On Thu, 25 Jul 2013 19:10:50 -0400 "Justin Piszcz" <jpiszcz@lucidpixels.com>
wrote:
> Did the fix by chance make it into 3.10.3?
No, it looks like it missed again. I gather there was a large inflow of
patches for -stable in the 3.11-rc1 merge window and Greg has been
processing
them in batches. Hopefully in 3.10.4.
The relevant patch is commit 30bc9b53878a9921b02e3 in mainline.
NeilBrown
--
Method to get patch via git and patch kernel:
$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
$ git log |grep 30bc9b53878a9921b02e3
commit 30bc9b53878a9921b02e3b5bc4283ac1c6de102a
$ git show 30bc9b53878a9921b02e3b5bc4283ac1c6de102a > /tmp/a
# patch -p1 < /tmp/a
patching file drivers/md/raid1.c
Hunk #1 succeeded at 1848 (offset -1 lines).
Hunk #2 succeeded at 1886 (offset -1 lines).
Hunk #3 succeeded at 1915 (offset -1 lines).
Reboot- tested, success, thanks..!
One follow-up question:
$ cat /sys/block/md1/md/mismatch_cnt
314112
-> On a live RAID-1 (root filesystem) without swap, is it normal to have
such a high mismatch_cnt even after a repair?
First repair:
Fri Jul 26 05:30:47 EDT 2013: The meta-device /dev/md1 has mismatch_cnt
314112 sectors.
Second repair:
Fri Jul 26 05:30:47 EDT 2013: The meta-device /dev/md1 has mismatch_cnt
313600 sectors.
Should I be concerned?
Testing the patch:
Personalities : [raid1]
md1 : active raid1 sdc2[0] sdb2[1]
233381376 blocks [2/2] [UU]
[>....................] check = 0.3% (838976/233381376)
finish=9.2min speed=419488K/sec
md0 : active raid1 sdc1[0] sdb1[1]
1048512 blocks [2/2] [UU]
Personalities : [raid1]
md1 : active raid1 sdc2[0] sdb2[1]
233381376 blocks [2/2] [UU]
[===============>.....] check = 77.5% (180889856/233381376)
finish=2.5min speed=342654K/sec
md0 : active raid1 sdc1[0] sdb1[1]
1048512 blocks [2/2] [UU]
Personalities : [raid1]
md1 : active raid1 sdc2[0] sdb2[1]
233381376 blocks [2/2] [UU]
md0 : active raid1 sdc1[0] sdb1[1]
1048512 blocks [2/2] [UU]
Justin.
next prev parent reply other threads:[~2013-07-26 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 10:26 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD) Justin Piszcz
2013-07-21 23:02 ` NeilBrown
2013-07-25 23:10 ` Justin Piszcz
2013-07-26 0:35 ` NeilBrown
2013-07-26 9:56 ` Justin Piszcz [this message]
2013-07-29 5:56 ` NeilBrown
2013-07-29 7:33 ` Justin Piszcz
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='001e01ce89e6$73f93b80$5bebb280$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).