adding drive to raidz1
Wes Morgan
morganw at chemikals.org
Fri Jun 19 00:45:06 UTC 2009
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?
More information about the freebsd-fs
mailing list