Messages per Month
14 messages in org.freebsd.freebsd-fsRe: adding drive to raidz1| 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: | Peter Jeremy (pete...@optushome.com.au) | |
| Date: | Jun 19, 2009 9:53:31 pm | |
| List: | org.freebsd.freebsd-fs | |
On 2009-Jun-18 23:12:16 -0500, "James R. Van Artsdalen"
<jame...@jrv.org> wrote:
As a feature suggestion why not reject an "zpool add" of a non-redundant vdev to a pool of redundant vdev's unless -f is given? A command of that sort is almost always a mistake so requiring -f would seem no hardship for anyone...
Agreed.
As was said, a vdev (ad7s1) cannot be removed from a pool, and a device cannot be added to a raidz.
Both these are unfortunate restrictions. I can understand that expanding a RAIDZ would be a fairly complex operation but it's probably the most requested feature. I'm surprised that Sun don't allow removing vdevs from a pool - it's orthogonal to adding a vdev to a pool and (eg) HP AdvFS allows both.
-- Peter Jeremy