>Most likely, the problem is that both the old and new disks have a pool
>named 'rpool'. You thus can't do anything like 'import rpool'.
>I'm assuming that you can at least see the old disk's pools via a plain
>'import', correct? Have you tried importing via UID rather than via
>name - also, try importing with a different mountpoint option.
>Last resort - boot from the LiveCD, import the old disks' rpool by UID,
>and then rename the whole pool something else (maybe 'oldrpool').
Thanks for the advice. I'll try importing by UID. As I mentioned in another
post, I can't actually get my solaris install on line until I spend most of a
day downloading a bunch of compiler packages and building the NIS wrapper for
my wireless card. Kind of a painful process that I'd rather not repeat.
Of course, I can always get the screwdrivers out and slap the old drive back
into the machine and dump all the necessary data onto a USB stick formatted
with fat32 and then get the screwdrivers back out and reinstall the new drive
and copy the data off of the stick, but this flies in the face of zfs' claim to
simplify administration of file systems. I was hoping for a more elegant
solution. One not involving screwdrivers, that is.
This stuff sure is tough.
I read the stuff in the zfs admin guide about clones and all that, but it
wasn't really sinking in too quickly and seems to involve acquainting myself
with enough new concepts that success seems a rather remote possibility.
Think I'll be sticking with UFS in the future. So far zfs has only made things
substantially less convenient for me.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
