Following up to myself as the Bug takes no end ...
On Tue, Sep 28, 1999 at 12:49:22AM +0200, Florian Lohoff wrote:
> The oops happens when
>
> booting
> autodetecting a raid (and start to rebuild)
> raidstop /dev/md0
> editing /etc/raidtab
> mkraid /dev/md0 (with the non email representable parm)
> Oops ... (After listing raid config verbose)
> /proc/mdstat
> Personalities : [raid5]
> read_ahead 1024 sectors
> md0 : active raid5 sdh1[5] sdg1[4] sdf1[3] sde1[2] sdd1[1]
> sdc1[0] 20923840 blocks level 5, 32k chunk, algorithm 2 [6/6]
> [UUUUUU] resync=0% finish=242243.4min
>
> No disk activity - raid5syncd crashed ?
> raidstop /dev/md0
> interrupting MD-thread pid 0
> <hang>
> ps auxw | grep raid
> root 130 0.0 0.0 0 0 ? SW< 00:14 0:00 (raid5d)
> root 155 0.0 0.1 1224 396 S0 D 00:15 0:00 raidstop /dev/md0
The bug continues ...
After rebooting the raid code goes into an infinity loop
-----------------------------------------
md: updating md0 RAID superblock on device
sdh1 [events: 00000002](write) sdh1's sb offset: 4184768
md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec.
md: using maximum available idle IO bandwith for reconstruction.
md: using 640k window.
sdg1 [events: 00000002](write) sdg1's sb offset: 4184768
sdf1 [events: 00000002](write) sdf1's sb offset: 4184768
sde1 [events: 00000002](write) sde1's sb offset: 4184768
sdd1 [events: 00000002]md: bug in file md.c, line 907
**********************************
* <COMPLETE RAID STATE PRINTOUT> *
**********************************
md0: <sdh1><sdg1><sdf1><sde1><sdd1><sdc1> array superblock:
SB: (V:0.90.0) ID:<26551975.79987239.baad6924.78f3546e> CT:37efec54
L5 S04184768 ND:6 RD:6 md0 LO:2 CS:32768
[...]
-----------------------------------------
This goes on forever until serial "break"ing into the
bootprom ...
Flo
--
Florian Lohoff [EMAIL PROTECTED] +49-5241-470566
... The failure can be random; however, when it does occur, it is
catastrophic and is repeatable ... Cisco Field Notice
