| From | Sent On | Attachments |
|---|---|---|
| Randy Bush | Jun 18, 2009 3:18 pm | |
| Andrew Snow | Jun 18, 2009 3:27 pm | |
| Dan Naumov | Jun 18, 2009 3:39 pm | |
| Randy Bush | Jun 18, 2009 3:51 pm | |
| Andrew Snow | Jun 18, 2009 3:54 pm | |
| Wes Morgan | Jun 18, 2009 5:44 pm | |
| Randy Bush | Jun 18, 2009 6:03 pm | |
| Wes Morgan | Jun 18, 2009 6:10 pm | |
| Randy Bush | Jun 18, 2009 6:20 pm | |
| James R. Van Artsdalen | Jun 18, 2009 9:11 pm | |
| Paul Schenkeveld | Jun 19, 2009 12:21 pm | |
| Peter Jeremy | Jun 19, 2009 9:53 pm | |
| Kip Macy | Jun 19, 2009 10:42 pm | |
| Pawel Jakub Dawidek | Aug 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?
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "free...@freebsd.org"





