Hello Noel,
Wednesday, June 28, 2006, 5:59:18 AM, you wrote:
ND a zpool remove/shrink type function is on our list of features we want
ND to add.
ND We have RFE
ND 4852783 reduce pool capacity
ND open to track this.
Is there someone actually working on this right now?
--
Best regards,
Hey Robert,
Well, not yet. Right now our top two priorities are improving
performance in multiple areas of zfs(soon there will be a performance
page tracking progess on the zfs community page), and also getting zfs
boot done. Hence, we're not currently working on heaps of brand new
Just wondered if there'd been any progress in this area?
Correct me if i'm wrong, but as it stands, there's no way
to remove a device you accidentally 'zpool add'ed without
destroying the pool.
On 12/06/06, Gregory Shaw [EMAIL PROTECTED] wrote:
Yes, if zpool remove works like you describe, it
Pardon me if this scenario has been discussed already, but I haven't
seen anything as yet.
I'd like to request a 'zpool evacuate pool device' command.
'zpool evacuate' would migrate the data from a disk device to other
disks in the pool.
Here's the scenario:
Say I have a small server
On 11/06/06, Gregory Shaw [EMAIL PROTECTED] wrote:
Pardon me if this scenario has been discussed already, but I haven't
seen anything as yet.
I'd like to request a 'zpool evacuate pool device' command.
'zpool evacuate' would migrate the data from a disk device to other
disks in the pool.
This only seems valuable in the case of an unreplicated pool. We
already have 'zpool offline' to take a device and prevent ZFS from
talking to it (because it's in the process of failing, perhaps). This
gives you what you want for mirrored and RAID-Z vdevs, since there's no
data to migrate
Yes, if zpool remove works like you describe, it does the same
thing. Is there a time frame for that feature?
Thanks!
On Jun 11, 2006, at 10:21 AM, Eric Schrock wrote:
This only seems valuable in the case of an unreplicated pool. We
already have 'zpool offline' to take a device and
