atom feed14 messages in org.freebsd.freebsd-fsRe: adding drive to raidz1
FromSent OnAttachments
Randy BushJun 18, 2009 3:18 pm 
Andrew SnowJun 18, 2009 3:27 pm 
Dan NaumovJun 18, 2009 3:39 pm 
Randy BushJun 18, 2009 3:51 pm 
Andrew SnowJun 18, 2009 3:54 pm 
Wes MorganJun 18, 2009 5:44 pm 
Randy BushJun 18, 2009 6:03 pm 
Wes MorganJun 18, 2009 6:10 pm 
Randy BushJun 18, 2009 6:20 pm 
James R. Van ArtsdalenJun 18, 2009 9:11 pm 
Paul SchenkeveldJun 19, 2009 12:21 pm 
Peter JeremyJun 19, 2009 9:53 pm 
Kip MacyJun 19, 2009 10:42 pm 
Pawel Jakub DawidekAug 5, 2009 7:22 am 
Subject:Re: adding drive to raidz1
From:Wes Morgan (morg@chemikals.org)
Date:Jun 18, 2009 6:10:00 pm
List:org.freebsd.freebsd-fs

On Thu, 18 Jun 2009, Randy Bush wrote:

The only way to "fix" this is just what everyone has said... Back up the data, destroy the pool and recreate.

done. worked. luckily this was a system in build.

When you do this, if you don't want to be using slices

i have nothing against slices

zpool create raidz somethingbesidestankfortheloveofgod ad4 ad5 ad6 ad7

she really does not care about the pool name. :)

And you'll be set. But you're using ad5s3 and ad6s3, are the first two slices in use?

on the two bootables s1 is a small gmirroed boot s2 is a non-mirrored swap s3 is pool

Just out of sheer curiosity, are all the slices and devices in the raidz the same size?