I *really* need suggestions here. This is a system which is supposed to
go production on Monday and I'm not feeling too good about this.
Here's some more output:
blah:/usr/src/linux/scripts/ksymoops# cat /proc/mdstat
Personalities : [raid0] [raid1]
read_ahead 1024 sectors
md2 : active raid1 md1[1](F) md0[0](F) 26876288 blocks [2/1] [_U]
md0 : active raid0 sdc1[2] sdb1[1] sda1[0] 26876352 blocks 16k chunks
md1 : active raid0 sdf1[2] sde1[1] sdd1[0] 26876352 blocks 16k chunks
unused devices: <none>
raid0_map bug: hash->zone0==NULL for block 151322631
attempt to access beyond end of device
09:00: rw=0, want=151322632, limit=26876352
dev 09:02 blksize=1024 blocknr=151322631 sector=302645262 size=1024
count=1
raid1: Disk failure on md0, disabling device.
Operation continuing on 1 devices
raid1: md2: rescheduling block 151322631
raid0_map bug: hash->zone0==NULL for block 587268096
attempt to access beyond end of device
09:01: rw=0, want=587268097, limit=26876352
dev 09:02 blksize=1024 blocknr=587268096 sector=1174536192 size=1024
count=1
raid1: only one disk left and IO error.
raid1: md2: rescheduling block 587268096
md: recovery thread got woken up ...
md2: no spare disk to reconstruct array! -- continuing in degraded mode
md: recovery thread finished ...
dirty sb detected, updating.
md: updating md2 RAID superblock on device
(skipping faulty md1 )
(skipping faulty md0 )
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/