Derek,
Have you tried doing a 'zpool replace poolname c1t53d0 c2t53d0'? I'm not
sure if this will work but worth a shot. You may still end up with a
complete resilver.
Thanks,
George
Derek E. Lewis wrote:
On Thu, 28 Dec 2006, George Wilson wrote:
You're best bet is to export and re-import the pool after moving
devices. You might also try to 'zpool offline' the device, move it and
then 'zpool online' it. This should force a reopen of the device and
then it would only have to resilver the transactions during the time
that the device was offline. I have not tried the later but it should
work.
George,
I haven't moved any devices around. I have two physical paths to the
JBOD, which allows the system to see all the disks on two different
controllers (c1t53d0 and c2t53d0 are already there). 'zfs
online/offline' and 'zfs import/export' aren't going to help at all
unless I physically swap the fibre paths. This won't work because I have
other pools on the JBOD.
If this were a production system, exporting the entire pool would not be
ideal, just to change the controller the mirrored pooldevs are using. If
ZFS cannot do this without (1) exporting the pool and importing it or
(2) doing a complete resilver of the disk(s), this sounds like a valid
RFE for a more intelligent 'zfs replace' or 'zfs attach/detach'.
Thanks,
Derek E. Lewis
[EMAIL PROTECTED]
http://delewis.blogspot.com
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
