Date: Thu, 18 Jun 2009 19:44:54 -0500 (CDT) From: Wes Morgan <morganw@chemikals.org> To: Andrew Snow <andrew@modulus.org> Cc: Randy Bush <randy@psg.com>, freebsd-fs@freebsd.org Subject: Re: adding drive to raidz1 Message-ID: <alpine.BSF.2.00.0906181941130.10212@ibyngvyr.purzvxnyf.bet> In-Reply-To: <4A3AC5B2.9010607@modulus.org> References: <m2bpol6v8r.wl%randy@psg.com> <4A3ABF76.3020905@modulus.org> <cf9b1ee00906181540w746edafi4a560b0925b14e27@mail.gmail.com> <m28wjp6tp2.wl%randy@psg.com> <4A3AC5B2.9010607@modulus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 19 Jun 2009, Andrew Snow wrote: > >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 0 >> raidz1 ONLINE 0 0 0 >> ad4s3 ONLINE 0 0 0 >> ad5s3 ONLINE 0 0 0 >> ad6s1 ONLINE 0 0 0 >> ad7s1 ONLINE 0 0 0 > > Here you have created a non-redundant stripe with two vdev members: > 1. a 3-disk RAIDZ1 and > 2.a single disk. > > So you can't ever remove the ad7s1 without data loss. > > If you haven't written anything to the pool since adding ad7s1, you can > probably yank the disk out and ignore any errors but the error messages will > never go away until you recreate the whole pool from scratch If you yank ad7s1 the pool will become unavailable. You could remove one of the slices in the raidz, though. The only way to "fix" this is just what everyone has said... Back up the data, destroy the pool and recreate. When you do this, if you don't want to be using slices, just "don't" -- use zpool create raidz somethingbesidestankfortheloveofgod ad4 ad5 ad6 ad7 And you'll be set. But you're using ad5s3 and ad6s3, are the first two slices in use?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0906181941130.10212>