I'm trying to build a raid array (preferrably RAID5, but 0 will do) on a
Sparc platform.  I've been 98% unsuccessful in doing so.  I've been
successful in getting a raid 0 array built under 2.2.1, but as soon as I
shut it down, it destroys itself, and is unrecoverable.  Also 2.2.1 appears
to be terribly buggy in the SMP code for sparc, and I can't really use it.

[root@tonga raidtools-0.90]# cat /proc/cpuinfo
cpu             : ROSS HyperSparc RT625 or RT626
fpu             : ROSS HyperSparc combined IU/FPU
promlib         : Version 3 Revision 2
prom            : 2.10
type            : sun4m
ncpus probed    : 4
ncpus active    : 4
Cpu0Bogo        : 89.70
Cpu1Bogo        : 89.90
Cpu2Bogo        : 89.90
Cpu3Bogo        : 89.90
MMU type        : ROSS HyperSparc
invall          : 0
invmm           : 0
invrnge         : 0
invpg           : 0
contexts        : 4096
CPU0            : online
CPU1            : online
CPU2            : online
CPU3            : online

[root@tonga raidtools-0.90]# cat /proc/mdstat 
Personalities :
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive

[root@tonga raidtools-0.90]# uname -a
Linux tonga.i-regatta.org 2.1.130 #4 SMP Wed Feb 17 16:33:00 EST 1999 sparc
unknown

[root@tonga raidtools-0.90]# ./mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/sdb4, 8841042kB, raid superblock at 8840960kB
disk 1: /dev/sdc2, 8841042kB, raid superblock at 8840960kB
disk 2: /dev/sde2, 8841042kB, raid superblock at 8840960kB
disk 3: /dev/sdf2, 8841042kB, raid superblock at 8840960kB
disk 4: /dev/sdi2, 8841042kB, raid superblock at 8840960kB
disk 5: /dev/sdj4, 8841042kB, raid superblock at 8840960kB
disk 6: /dev/sdk2, 8841042kB, raid superblock at 8840960kB
disk 7: /dev/sdl4, 8841042kB, raid superblock at 8840960kB
disk 8: /dev/sdm4, 8841042kB, raid superblock at 8840960kB
disk 9: /dev/sdn4, 8841042kB, raid superblock at 8840960kB
mkraid: aborted

[root@tonga raidtools-0.90]# cat /proc/mdstat 
Personalities :
read_ahead not set
md0 : inactive
md1 : inactive
md2 : inactive
md3 : inactive

There are no messages sent to console upon failure.

Does anyone out there know the magic wand tricks to make this work, or am I
just a little to early in the development to get something that works yet?

-Chris

Reply via email to