I second that.
This is exactly what happened to me.
There is a bug (ID 4852783) that is in State "6-Fix Understood" but it is
unchanged since February 2010.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris
You're right - in my company (a very big one) we just stumbled across this as
well and we're strongly considering not using ZFS because of it.
It's easy to type zpool add when you meant zpool replace - and then you can go
rebuild your box because it was the root pool. Nice.
At the very least, "
They also mentioned this at some of the ZFS talks at LISA 2008.The general
argument is that, while plenty of hobbyists are clamoring for this, not enough
paying customers are asking to make it a high enough priority to get done.
If you think about it, the code is not only complicated but wi
If I remember right, the code needed for this has implications for a lot of
things:
- defrag
- adding disks to raidz zvols
- removing disks from vols
- restriping volumes (to give consistent performance after expansion)
In fact, I just found the question I asked a year or so back, which had a go
> "mb" == Mike Brancato <[EMAIL PROTECTED]> writes:
mb> if a 4x100GB raidz only used 150GB of space, one could do
mb> 'zpool remove tank c0t3d0' and data residing on c0t3d0 would
mb> be migrated to other disks in the raidz.
that sounds like in-place changing of stripe width, and w
Well, I knew it wasn't available. I meant to ask what is the status of the
development of the feature? Not started, I presume.
Is there no timeline?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Mike Brancato wrote:
> I've seen discussions as far back as 2006 that say development is underway to
> allow the addition and remove of disks in a raidz vdev to grow/shrink the
> group. Meaning, if a 4x100GB raidz only used 150GB of space, one could do
> 'zpool remove tank c0t3d0' and data resi
I've seen discussions as far back as 2006 that say development is underway to
allow the addition and remove of disks in a raidz vdev to grow/shrink the
group. Meaning, if a 4x100GB raidz only used 150GB of space, one could do
'zpool remove tank c0t3d0' and data residing on c0t3d0 would be migra