Date: Thu, 18 Jun 2009 18:04:17 -0700 From: Randy Bush <randy@psg.com> To: Wes Morgan <morganw@chemikals.org> Cc: freebsd-fs@freebsd.org Subject: Re: adding drive to raidz1 Message-ID: <m2ws79590u.wl%randy@psg.com> In-Reply-To: <alpine.BSF.2.00.0906181941130.10212@ibyngvyr.purzvxnyf.bet> References: <m2bpol6v8r.wl%randy@psg.com> <4A3ABF76.3020905@modulus.org> <cf9b1ee00906181540w746edafi4a560b0925b14e27@mail.gmail.com> <m28wjp6tp2.wl%randy@psg.com> <4A3AC5B2.9010607@modulus.org> <alpine.BSF.2.00.0906181941130.10212@ibyngvyr.purzvxnyf.bet>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
randy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2ws79590u.wl%randy>