Hey,

-----Original Message-----
From: NeilBrown [mailto:neilb@suse.de]
Sent: Monday, August 19, 2013 10:04 AM
To: Blaesing, Matthias (KC-IT)
Cc: linux-raid@vger.kernel.org
Subject: Re: Recovery of RAID1 fails (added disks stays as spare)

On Mon, 19 Aug 2013 07:48:20 +0000 [off-list ref] wrote:

quoted

Hey,

quoted

quoted

Strange.  I would definitely have expected one of those to start the
recovery.
Does anything appear in the kernel logs (e.g. output of 'dmesg')?

Please see the attaches boot.msg - from my perspective it only

confirms the results

quoted

gained from the /proc/mdstat and mdadm output.

I guess I should have been more explicit.
It looks like you have just attached a log of what happened at boot.
I mean does anything appear in the dmesg output when you try to add the
spare
device to the array.

You mean this (the first lines should be the result of mdadm --fail and mdadm --remove):

Aug 19 10:54:28 s15434194 kernel: [2149292.392602] md/raid1:md3: Disk failure on sda3, disabling device.
Aug 19 10:54:28 s15434194 kernel: [2149292.392603] md/raid1:md3: Operation continuing on 1 devices.
Aug 19 10:54:44 s15434194 kernel: [2149307.970181] md: unbind<sda3>
Aug 19 10:54:44 s15434194 kernel: [2149308.033073] md: export_rdev(sda3)
Aug 19 10:56:46 s15434194 kernel: [2149430.007318] md: bind<sda3>
Aug 19 10:56:46 s15434194 kernel: [2149430.043534] RAID1 conf printout:
Aug 19 10:56:46 s15434194 kernel: [2149430.043542]  --- wd:1 rd:2
Aug 19 10:56:46 s15434194 kernel: [2149430.043549]  disk 0, wo:0, o:1, dev:sdb3
Aug 19 10:56:46 s15434194 kernel: [2149430.043554]  disk 1, wo:1, o:1, dev:sda3
Aug 19 10:56:46 s15434194 kernel: [2149430.043833] md: recovery of RAID array md3
Aug 19 10:56:46 s15434194 kernel: [2149430.043841] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
Aug 19 10:56:46 s15434194 kernel: [2149430.043847] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Aug 19 10:56:46 s15434194 kernel: [2149430.043857] md: using 128k window, over a total of 970888192k.


Aug 20 02:27:56 s15434194 kernel: [2205289.321866] md: md3: recovery done.
Aug 20 02:27:57 s15434194 kernel: [2205300.981062] RAID1 conf printout:
Aug 20 02:27:57 s15434194 kernel: [2205300.981070]  --- wd:1 rd:2
Aug 20 02:27:57 s15434194 kernel: [2205300.981077]  disk 0, wo:0, o:1, dev:sdb3
Aug 20 02:27:57 s15434194 kernel: [2205300.981083]  disk 1, wo:1, o:1, dev:sda3
Aug 20 02:27:57 s15434194 kernel: [2205301.025544] RAID1 conf printout:
Aug 20 02:27:57 s15434194 kernel: [2205301.025551]  --- wd:1 rd:2
Aug 20 02:27:57 s15434194 kernel: [2205301.025557]  disk 0, wo:0, o:1, dev:sdb3

While rebuilding I also see read-errors from sdb:

Aug 20 02:27:54 s15434194 kernel: [2205267.984530] md/raid1:md3: sdb: unrecoverable I/O read error for block 1941766272

I guess as this affects the source, it should not affect the move of sda to be active.


Mit freundlichen Grüßen

Matthias Bläsing
Abt IT
KompetenzCenter

Tel.: 02351 950-344
Fax.: 02351 950-222
mailto: matthias.blaesing@persona.de
www.persona.de




persona service Verwaltungs AG & Co. KG 
Freisenbergstra�e 31 � 58513 L�denscheid  
Tel.: (02351) 950-0 � Fax: (02351) 950-222 
Sitz L�denscheid � Registergericht Iserlohn, HRA Nr. 2930

pers�nlich haftende Gesellschafterin: persona service AG
Gartenstra�e 93 � CH-4002 Basel
Handelsregister Basel, Nr. CH-270.3.012.836-8
diese vertreten durch den Verwaltungsrat:
Georg Breucker (Pr�sident) und Dr. Sebastian Burckhardt
www.persona.de