On Sat, Dec 20, 2003 at 10:51:06AM -0600, Greg Oster wrote:
> 
> Hi
> 
> RAIDframe has always had the notion of "rows" and "columns" of
> components.  While this interface has been exported to the world, the
> RAIDframe internals really only support the concept of "columns", and
> while much todo is made about traversing "each row", only a single row
> is supported within the kernel.  In particular, upon code inspection,
> you will find many of these lines:
> 
>  RF_ASSERT(raidPtr->numRow == 1);
> 
> sprinkled about, effectively limiting the number of rows to just the
> one.
> 
> 
> I am therefore proposing to entirely remove from the kernel the
> feigned support for multiple rows.  Configuration files, component
> labels, etc. will all continue to have the "row" field, but this will
> end up getting hard-coded to "1 row" where needed, and "row 0" where a
> row value is still required.  Nothing wil change with respect to
> configuration of RAID sets.  /usr/include/dev/raidframe/raidframevar.h
> will be changed, but those changes will only be related to kernel
> internals, and none of the structures used for passing configuration
> information will change.

Hi,
would a raid1 with n*2 disks continue to works (e.g. something like:
           START array
           # numRow numCol numSpare
           1 4 0

           START disks
           /dev/sd1e
           /dev/sd2e
           /dev/sd3e
           /dev/sd4e

           START layout
           # sectPerSU SUsPerParityUnit SUsPerReconUnit RAID_level_5
           32 1 1 1

           START queue
           fifo 100

I have setups like that.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 23 ans d'experience feront toujours la difference
--