The ability to expand (and, to a less extent, shrink) a RAIDZ or RAIDZ2
device is actually one of the more critical missing features from ZFS,
IMHO. It is very common for folks to add additional shelf or shelves
into an existing array setup, and if you have created a pool which uses
RAIDZ
Matthew Ahrens wrote:
Erik Trimble wrote:
The ability to expand (and, to a less extent, shrink) a RAIDZ or
RAIDZ2 device is actually one of the more critical missing features
from ZFS, IMHO. It is very common for folks to add additional shelf
or shelves into an existing array setup, and if
Hello Matthew,
Tuesday, October 24, 2006, 3:36:13 AM, you wrote:
MA FYI, we're working on being able to shrink pools with no restrictions.
MA Unfortunately I don't have an ETA for you on this, though.
That's great!
MA And as I'm sure you know, you can always grow pools :-)
Well, partially -
Erik Trimble wrote:
Matthew Ahrens wrote:
Erik Trimble wrote:
The ability to expand (and, to a less extent, shrink) a RAIDZ or
RAIDZ2 device is actually one of the more critical missing features
from ZFS, IMHO. It is very common for folks to add additional shelf
or shelves into an existing
Hello,
Shrinking the vdevs requires moving data. Once you move data, you've
got to either invalidate the snapshots or update them. I think that
will be one of the more difficult parts.
Updating snapshots would be non-trivial, but doable. Perhaps some sort
of reverse mapping or brute force
Shrinking the vdevs requires moving data. Once you move data, you've
got to either invalidate the snapshots or update them. I think that
will be one of the more difficult parts.
Updating snapshots would be non-trivial, but doable. Perhaps some sort
of reverse mapping or brute force
Hello Jeremy,
Monday, October 23, 2006, 5:04:09 PM, you wrote:
JT Hello,
Shrinking the vdevs requires moving data. Once you move data, you've
got to either invalidate the snapshots or update them. I think that
will be one of the more difficult parts.
JT Updating snapshots would be
Robert Milkowski wrote:
Hello Jeremy,
Monday, October 23, 2006, 5:04:09 PM, you wrote:
JT Hello,
Shrinking the vdevs requires moving data. Once you move data, you've
got to either invalidate the snapshots or update them. I think that
will be one of the more difficult parts.
JT Updating
On Sun, 2006-10-15 at 20:54 -0700, Matthew Ahrens wrote:
Frank Cusack wrote:
Someone said being able to add devices to a raidz vdev is on the todo list.
Don't hold your breath. This isn't being worked on, or on anyone's todo
list at this point, and implementing it would be pretty
Hi guys,
On 16 Oct 2006, at 14:30, Bill Sommerfeld wrote:
On Sun, 2006-10-15 at 20:54 -0700, Matthew Ahrens wrote:
Frank Cusack wrote:
Someone said being able to add devices to a raidz vdev is on the
todo list.
Don't hold your breath. This isn't being worked on, or on
anyone's todo
On 16 Oct 2006, at 14:30, Bill Sommerfeld wrote:
On Sun, 2006-10-15 at 20:54 -0700, Matthew Ahrens wrote:
Frank Cusack wrote:
Someone said being able to add devices to a raidz vdev is on the
todo list.
Don't hold your breath. This isn't being worked on, or on
anyone's todo
Recently, I was in a position where I was aiding someone in
configuring five disks in RAID-Z1, and we were discussing whether or
not it would be possible to add (not replace) disks to the pool
without destroying and recreating the filesystem.
As far as I know, this is not currently possible (as
12 matches
Mail list logo
