Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 02 Aug 2014 18:33:38 -0400
From:      Daniel Staal <>
Subject:   Re: gvinum raid5 vs. ZFS raidz
Message-ID:  <2D72AC9FF5B82553FEF7D3EB@[]>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
--As of August 2, 2014 1:21:54 AM -0500, Scott Bennett is alleged to have 

>>> Does not support migration to any other		Does not support migration
>>> RAID levels or their equivalents.		between raidz levels, even by
>> Correct. Once you have created a vdev, that vdev must remain the same
>> type. You can add mirrors to a mirror vdev, but you cannot add drives or
>> change raid level to raidz1, raidz2, or raidz3 vdevs.
>      Too bad.  Increasing the raidz level ought to be not much more
> difficult than growing the raidz device by adding more spindles.  Doing
> the latter ought to be no more difficult that doing it with gvinum's
> stripe or raid5 devices.  Perhaps the ZFS developers will eventually
> implement these capabilities.  (A side thought:  gstripe and graid3
> devices ought also to be expandable in this manner, although the resulting
> number of graid3 components would still need to be 2^n + 1.)

--As for the rest, it is mine.

There actually is a semi-simple way, even if it's not direct...

You can 'send' a ZFS filesystem to a backup drive, and then 'receive' it 
back to a new pool.  It will keep all file and volume level options when 
you do that, but the pools can be set up differently.  It's not something 
you can do in-place, but it's not hard either.

(Basically, it's a simplified 'backup and restore to new setup', but it is 
majorly simplified.)

Daniel T. Staal

This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.

Want to link to this message? Use this URL: <>