Re: disklabel problems on 3TB disc

[buhrow%lothlorien.nfbcal.org@localhost (Brian Buhrow)]

        Hello.  Below is a /etc/raid0.conf I use with this configuration.
I've been running this way for at least 2 years.
        As to the question about how to replace a failed component with a
slightly smaller one, the answeris you don't.  If you use 3TB disks as your
raid components, you'd better  have 3TB disks as replacements.
        If you  don't want to use the entire disk, then use gpt(8) partitions
on the disks, and build the raid set in the gpt partitions.  In that case,
the devices would look like:
/dev/dk0
/dev/dk1
/dev/dk2
etc.
(This is for the components of the raid set, in raidx.conf, in case that
isn't clear.)
        Then, build another gpt partition on the raid set itself, and it will
be yet another /dev/dk device.

Hope that helps.
-Brian


#Raid Configuration File for fserv1.via.net (BB 4/12/2006)
#Brian Buhrow
#Describe the size of the array, including spares
START array
#numrow numcol numspare
1 8 1

#Disk section
#Stripe across two twa(4) cards.
START disks
/dev/ld0d
/dev/ld4d
/dev/ld1d
/dev/ld5d
/dev/ld2d
/dev/ld6d
/dev/ld3d
/dev/ld7d

#Layout section.  We'll use 63 sectors per stripe unit, 1 parity unit per 
#stripe unit, 1 parity unit per stripe, and raid level 5.
START layout
#SectperSu SusperParityUnit SusperReconUnit Raid_level
64 1 1 5

#Fifo section.  We'll use 100 outstanding requests as a start.
START queue
fifo 100

#spare section
#No spares.
#START spare
#/dev/wd8a