On Sun, Feb 24, 2013 at 07:41:21PM +0100, Manuel Bouyer wrote:
On Sun, Feb 24, 2013 at 07:27:19PM +0000, Philip Mueller wrote:
[...]
What is the next step?
Create gpt+ shifted partition?
create a gpt partition on the raid volume a newfs it.
then create a second gpt partition on wd3, type ffs, which is the
same size as the gpt partition on the raid, but with start shifted
by 64 or 128 sectors (I though it was 128 but David may be right about it
being 64).
That is just wrong. My understanding is that the wants to add wd3 later
as another part of the raid1.
This is what i did with adding two 3TB disks:
---------------------------------------------------------
# Add wedge to wd0
gpt create wd0
gpt add -b 64 -s 5851054080 -t raid wd0
dkctl wd0 addwedge Disk_1 64 5851054080 raidframe
# Configure the raid
raidctl -v -C /root/raid0.conf raid0
# Set the serial number
raidctl -v -I $timstamp raid0
# Initialize the raid
raidctl -v -i raid0
# Check initialize
raidctl -v -s raid0
# Add a wedge to raid0
gpt create raid0
gpt add -b 128 raid0
dkctl raid0 addwedge Raid0 128 5851053855 ffs
# Create the file system on the raid
newfs -O 2 -b 32k -f 4k -i 256k /dev/rdk1
# Mount it
mount /dev/dk1 /mnt
# Reboot
# Configure the raid again
raidctl -v -C /root/raid0.conf raid0
# Add wedge to wd1
gpt create wd1
gpt add -b 64 -s 5851054080 -t raid wd1
dkctl wd3 addwedge Disk_2 64 5851054080 raidframe
raidctl -a /dev/dk1 raid0
raidctl -F component1 raid0
# Set auto config
raidctl -v -A yes raid0
# Mount it
mount /dev/dk2 /mnt
---------------------------------------------------------
The only issue is that I have to use dk2 and not the id of the wedge
for mounting :(
Bernd