Ive got strange raid2 behaiver happening, ive got this raidtab:
----- raidtab -----
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
persistent-superblock 1
chunk-size 8
device /dev/hde1
raid-disk 0
device /dev/hdi1
raid-disk 1
raiddev /dev/md1
raid-level 0
nr-raid-disks 2
persistent-superblock 1
chunk-size 8
device /dev/hdf1
raid-disk 0
device /dev/hdj1
raid-disk 1
# not in use right now
#raiddev /dev/md2
# raid-level 0
# nr-raid-disks 2
# persistent-superblock 1
# chunk-size 8
# device /dev/hdg1
# raid-disk 0
# device /dev/hdk1
# raid-disk 1
raiddev /dev/md3
raid-level 0
nr-raid-disks 2
persistent-superblock 1
chunk-size 8
device /dev/hdh1
raid-disk 0
device /dev/hdl1
raid-disk 1
----- raidtab -----
Im missing one disk on the md2 so im not using that right now but that
should not affect the raid2 or make this happen:
# raidstop --all /dev/md3
/dev/md3: Device or resource busy
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid5] [multipath]
read_ahead 1024 sectors
md3 : active raid0 hdl1[1] hdh1[0]
240688000 blocks 8k chunks
unused devices: <none>
md0 and md1 gets turned off just fine, but not md3 ????
I will try and rebuild the raid and mode md3 disks to md2 and see what
happens.
# uname -a
Linux odd 2.4.19-pre9 #1 SMP Wed May 29 08:46:00 CEST 2002 i686 unknown
There is no new 2.4.19-pre patch out from what i can find.
Thanks in advance for the help.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri May 31 2002 - 22:00:28 EST