From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Backlund Subject: Re: md raid10 regression in 2.6.27.4 (possibly earlier) Date: Mon, 03 Nov 2008 20:09:34 +0200 Message-ID: <490F3E5E.1040801@mandriva.org> References: <490D8EBF.8050400@rabbit.us> <490DE55F.6080600@mandriva.org> <490E3CF9.20208@mandriva.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <490E3CF9.20208@mandriva.org> Sender: linux-raid-owner@vger.kernel.org To: linux-raid@vger.kernel.org List-Id: linux-raid.ids Thomas Backlund skrev: > Thomas Backlund skrev: >> Peter Rabbitson skrev: >>> Hi, >>> >>> Some weeks ago I upgraded from 2.6.23 to 2.6.27.4. After a failed hard >>> drive I realized that re-adding drives to a degraded raid10 no longer >>> works (it adds the drive as a spare and never starts a resync). Booting >>> back into the old .23 kernel allowed me to complete and resync the array >>> as usual. Attached find a test case reliably failing on vanilla 2.6.27.4 >>> with no patches. >>> >> >> I've just been hit with the same problem... >> >> I have a brand new server setup with 2.6.27.4 x86_64 kernel and a mix of >> raid0, raid1, raid5 & raid10 partitions like this: > > And an extra datapoint. > > Booting into 2.6.26.5 triggers an instant resync of the spare disks, so > it means we have a regression between 2.6.26.5 and 2.6.27.4 > > If no-one have a good suggestion to try, I'll start bisecting tomorrow... Ands some more info... After rebooting into 2.6.27.4 I got this again: md5 : active raid1 sdb7[1] sda7[0] sdd7[2] 530048 blocks [4/3] [UUU_] md3 : active raid10 sdc5[4](S) sda5[3] sdd5[0] sdb5[1] 20980608 blocks 64K chunks 2 near-copies [4/3] [UU_U] md2 : active raid10 sdc3[4](S) sda3[5](S) sdd3[3] sdb3[1] 41961600 blocks 64K chunks 2 near-copies [4/2] [_U_U] So it seems it's not only raid10 affected.... and here how they are started: [root@tmb ~]# cat /etc/udev/rules.d/70-mdadm.rules SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_FS_TYPE}=="linux_raid*", \ RUN+="/sbin/mdadm --incremental --run --scan $root/%k" -- Thomas