Date: Wed, 23 Apr 2014 13:03:19 +0100 From: Tom Evans <tevans.uk@googlemail.com> To: Hugo Lombard <hal@elizium.za.net> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: ZFS unable to import pool Message-ID: <CAFHbX1JWKGNkTcOxryE105zhBGoxRuf1UNzP5Qk4oJ4jgqSOKQ@mail.gmail.com> In-Reply-To: <20140423120042.GK2830@sludge.elizium.za.net> References: <B493BD80-CDC2-4BA6-AC14-AE16B373A051@icloud.com> <20140423064203.GD2830@sludge.elizium.za.net> <B1024D84-EBBE-4A9B-82C4-5C19B5A66B60@icloud.com> <20140423080056.GE2830@sludge.elizium.za.net> <20140423091852.GH2830@sludge.elizium.za.net> <20140423100126.GJ2830@sludge.elizium.za.net> <5357937D.4080302@gmail.com> <20140423120042.GK2830@sludge.elizium.za.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 23, 2014 at 1:00 PM, Hugo Lombard <hal@elizium.za.net> wrote: > [1] Trying to add a single device resulted in zpool add complaining > with: > > mismatched replication level: pool uses raidz and new vdev is disk > > and trying it with three disks said: > > mismatched replication level: pool uses 5-way raidz and new vdev uses 3-way raidz > > > [2] http://lists.freebsd.org/pipermail/freebsd-fs/2014-April/019340.html > In earlier versions of ZFS, ISTR that this check did not exist, and you could do exactly this - expand a pool by adding a vdev that is not of the same "class" as the existing vdevs on the pool. If the vdev still existed, this could be fixed by a dumping the data somewhere, re-creating the pool with the correct vdevs, and restoring the data. Otherwise, I think the only solution is to restore from backup. Perhaps you could roll back the txg before the vdev was added, that is way above my level of knowledge. Cheers Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHbX1JWKGNkTcOxryE105zhBGoxRuf1UNzP5Qk4oJ4jgqSOKQ>