From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?BERTRAND_Jo=EBl?= Subject: Re: 2.6.23.1: mdadm/raid5 hung/d-state Date: Tue, 06 Nov 2007 13:20:45 +0100 Message-ID: <47305C1D.5070500@systella.fr> References: <18222.16003.92062.970530@notabene.brown> <47303FB8.7000801@systella.fr> <47305288.8020307@systella.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Justin Piszcz Cc: Dan Williams , Neil Brown , linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org List-Id: linux-raid.ids Justin Piszcz wrote: >=20 >=20 > On Tue, 6 Nov 2007, BERTRAND Jo=EBl wrote: >=20 >> Justin Piszcz wrote: >>> >>> >>> On Tue, 6 Nov 2007, BERTRAND Jo=EBl wrote: >>> >>>> Done. Here is obtained ouput : >>>> >>>> [ 1265.899068] check 4: state 0x6 toread 0000000000000000 read=20 >>>> 0000000000000000 write fffff800fdd4e360 written 0000000000000000 >>>> [ 1265.941328] check 3: state 0x1 toread 0000000000000000 read=20 >>>> 0000000000000000 write 0000000000000000 written 0000000000000000 >>>> [ 1265.972129] check 2: state 0x1 toread 0000000000000000 read=20 >>>> 0000000000000000 write 0000000000000000 written 0000000000000000 >>>> >>>> >>>> For information, after crash, I have : >>>> >>>> Root poulenc:[/sys/block] > cat /proc/mdstat >>>> Personalities : [raid1] [raid6] [raid5] [raid4] >>>> md_d0 : active raid5 sdc1[0] sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[= 1] >>>> 1464725760 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUU= UU] >>>> >>>> Regards, >>>> >>>> JKB >>> >>> After the crash it is not 'resyncing' ? >> >> No, it isn't... >> >> JKB >> >=20 > After any crash/unclean shutdown the RAID should resync, if it doesn'= t,=20 > that's not good, I'd suggest running a raid check. >=20 > The 'repair' is supposed to clean it, in some cases (md0=3Dswap) it g= ets=20 > dirty again. >=20 > Tue May 8 09:19:54 EDT 2007: Executing RAID health check for /dev/md= 0... > Tue May 8 09:19:55 EDT 2007: Executing RAID health check for /dev/md= 1... > Tue May 8 09:19:56 EDT 2007: Executing RAID health check for /dev/md= 2... > Tue May 8 09:19:57 EDT 2007: Executing RAID health check for /dev/md= 3... > Tue May 8 10:09:58 EDT 2007: cat /sys/block/md0/md/mismatch_cnt > Tue May 8 10:09:58 EDT 2007: 2176 > Tue May 8 10:09:58 EDT 2007: cat /sys/block/md1/md/mismatch_cnt > Tue May 8 10:09:58 EDT 2007: 0 > Tue May 8 10:09:58 EDT 2007: cat /sys/block/md2/md/mismatch_cnt > Tue May 8 10:09:58 EDT 2007: 0 > Tue May 8 10:09:58 EDT 2007: cat /sys/block/md3/md/mismatch_cnt > Tue May 8 10:09:58 EDT 2007: 0 > Tue May 8 10:09:58 EDT 2007: The meta-device /dev/md0 has 2176=20 > mismatched sectors. > Tue May 8 10:09:58 EDT 2007: Executing repair on /dev/md0 > Tue May 8 10:09:59 EDT 2007: The meta-device /dev/md1 has no mismatc= hed=20 > sectors. > Tue May 8 10:10:00 EDT 2007: The meta-device /dev/md2 has no mismatc= hed=20 > sectors. > Tue May 8 10:10:01 EDT 2007: The meta-device /dev/md3 has no mismatc= hed=20 > sectors. > Tue May 8 10:20:02 EDT 2007: All devices are clean... > Tue May 8 10:20:02 EDT 2007: cat /sys/block/md0/md/mismatch_cnt > Tue May 8 10:20:02 EDT 2007: 2176 > Tue May 8 10:20:02 EDT 2007: cat /sys/block/md1/md/mismatch_cnt > Tue May 8 10:20:02 EDT 2007: 0 > Tue May 8 10:20:02 EDT 2007: cat /sys/block/md2/md/mismatch_cnt > Tue May 8 10:20:02 EDT 2007: 0 > Tue May 8 10:20:02 EDT 2007: cat /sys/block/md3/md/mismatch_cnt > Tue May 8 10:20:02 EDT 2007: 0 I cannot repair this raid volume. I cannot reboot server without=20 sending stop+A. init 6 stops at "INIT:". After reboot, md0 is=20 resynchronized. Regards, JKB - To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html