Problem adding second mirror to zpool

[David J. Weller-Fahy]

* Paul Kraus <paul at kraus-haus.org> [2014-12-05 12:26 -0500]:
>On 12/5/14 6:19, David J. Weller-Fahy wrote:
>>* David J. Weller-Fahy <dave+lists.freebsd-questions at caterva.org>
>>[2014-12-04 21:03 -0500]:
>>>#v+
>>>root at nastie:~ # zpool attach pool \
>>>    /dev/gptid/c6ede2a4-78a6-11e4-8646-0014222d98da \
>>>    /dev/gptid/fadbb43d-7aa2-11e4-8452-0014222d98da
>>>cannot attach /dev/gptid/fadbb43d-7aa2-11e4-8452-0014222d98da to \
>>>    /dev/gptid/c6ede2a4-78a6-11e4-8646-0014222d98da: no such device in
>>>pool
>>>#v-
>
>The error is about the first device not being in the zpool, so I would 
>first make sure that I shell completed the device name (path) instead 
>of cut and paste or typing. A hidden character (backspace maybe) could 
>make this fail.

I made sure I was using shell completion, and tried from a terminal on 
the device (rather than sshing into the box), with the same error.

>If that fails I would try exporting the importing the zpool.

I tried booting from a Live CD (USB-key, but same idea), imported the 
zpool, exported the zpool, then imported it again, and finally executed 
the same commands.  Same error.

I then tried removing the second partition from the first mirror, so 
there were only two drives in the pool, neither mirrored, and tried to 
add the partition again.  Same error.

I then decided I needed more information, and tried to get it by 
executing `zdb -C`... which gave me a new error!  The new error follows.

#v+
root@~ # zdb -C
cannot open '/boot/zfs/zpool.cache': No such file or directory
#v-

However, I believe that's just because I'm in a live boot that doesn't 
normally contain my zpool.  Looking in pool/root/boot/zfs I see the 
zpool.cache file, so this is probably a red herring.

At this point I'm not sure what to try other than copying all the data 
off the zpool, destroying the zpool entirely, and adding all the disks 
at once during creation.  Any other suggestions?

>I saw your comment about size, but error is not related to size of the 
>new device, but that the zpool command cannot find the existing device 
>in the zpool to attach the new one to. You _may_ still have a space 
>issue, but that is not this error.

Yes: the comment about size was more about what would be needed to copy 
all the data off the zpool if I needed to wipe everything and start 
over.  It was not about the space on the zpool or sizes needed for the 
zpool, but I may have been unclear.

Regards,
-- 
dave [ please don't CC me ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 173 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20141205/02332952/attachment.sig>