On Wednesday February 20, brinley.craig@godfreyhirst.com wrote:
> Hi All,
>
> i stuffed up the setup of the raid and have 3 partitions in a raid 1 array,
> instead of 2 partitions and a hot spare. i also want to move the partitions
> around for better load balancing on the scsi channels.
> i dont want to blow away the data, so i tried to raidsetfaulty,
> but i get an error. i also tried mdctl, but get some wierd results.
> may indicate something? or maybe just a simple syntax error.
> when i examine each drive in the array, the state info looks corrupt?
> thanks for any help.
> Brin
>
>
> /sbin/raidsetfaulty /dev/md0 /dev/sdj1
> /dev/md0: can not set disk faulty: invalid argument.
> /sbin/mdctl --fail /dev/md0 /dev/sdj1
> mdctl: set disk faulty failed for /dev/sdj1: Invalid argument
>
> proc
> ------
> md0 : active raid1 sdj1[1] sdb1[2] sda1[0] 14272 blocks [3/3] [UUU]
> md1 : active raid1 sda4[0] 8296896 blocks [3/1] [U__]
>
> uname
> ---------
> Linux sunny 2.2.19-6.2.12smp #1 SMP Fri Oct 26 12:56:49 EDT 2001 sparc64
^^^^^^^ ^^^^^^^
RAID in 2.2 has problems on SPARC. The superblock contains a 64bit
value which is would not normally be 64bit aligned. i386 machines
are happy with it being 32bit aligned and the resulting superblock is
1024 bytes. Sparc pads to a 64bit alignment and the resulting
superblock is 1028 (I think) bytes which is just wrong.
in 2.4, this 64bit value is replaced by 2 32bit values and things are
happiers.
mdctl assumes a the superblock looks like it does on i386 machines,
and on 2.4 machines, and so reports bogus information when you
do mdctl --examine.
As for the orignal problem: I'm afraid that raid is not being
actively support in 2.2 (that I know of). Is there any chance of
upgrading to 2.4???
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
