On Sun, Feb 24, 2013 at 08:41:53PM +0000, Philip Mueller wrote: > On 24.02.2013 18:41, 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). > > > spectre# gpt create raid1 > spectre# gpt add -t ffs raid1 > Partition added, use: > dkctl raid1 addwedge <wedgename> 34 3907028925 <type> > to create a wedge for it > spectre# dkctl raid1 addwedge dk1 34 3907028925 ffs > dk1 created successfully. > spectre# newfs -O2 dk1 > /dev/rdk1: 1907729.0MB (3907028920 sectors) block size 32768, > fragment size 4096 > using 2570 cylinder groups of 742.31MB, 23754 blks, 46848 inodes. > super-block backups (for fsck_ffs -b #) at: > 192, 1520448, 3040704, 4560960, 6081216, 7601472, 9121728, 10641984, > 12162240, > ............................................................................... > spectre# raidctl -uv raid1 > spectre# gpt show wd3 > start size index contents > 0 1 PMBR > 1 1 Pri GPT header > 2 32 Pri GPT table > 34 3907029101 1 GPT part - NetBSD RAIDFrame component > 3907029135 32 Sec GPT table > 3907029167 1 Sec GPT header > > The Problem is now, that there is already a gpt table on wd3. > How could be create a second gpt partition with shift of 64 sectors?
I don't remmember but man gpt should tell you. The offset of the new partition should be 34 (offset of raid partition on wd3) + 64 (space used by raidframe metadata) + 34 (offset of ffs partition in raid volume) -- Manuel Bouyer <[email protected]> NetBSD: 26 ans d'experience feront toujours la difference --
