[EMAIL PROTECTED]:~# zpool import pool: new_zpool id: 3042040702885268372 state: ONLINE action: The pool can be imported using its name or numeric identifier. config:
new_zpool ONLINE c0t2d0s6 ONLINE It shows that there is one filesystem available for import on one of my disks. Here is a list of what zpools I have associated now: [EMAIL PROTECTED]:~# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT u01 354G 254K 354G 0% ONLINE - u02 354G 150K 354G 0% ONLINE - Now I run the import command. Note, I can even rename the pool when I import it. so, for example, you could import your "newhome" volume as "home". Here I will import the "new_zpool" as "zpool". [EMAIL PROTECTED]:~# zpool import new_zpool zpool [EMAIL PROTECTED]:~# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT u01 354G 254K 354G 0% ONLINE - u02 354G 150K 354G 0% ONLINE - zpool 354G 500K 354G 0% ONLINE - [/i] Not there yet, though. It works pretty much like you say, thanks. I had to % zpool export home before I could successfully 'import', since there was a faulty home - - - - FAULTED - probably from my last start without the home. In the end, after % zpool import newhome home it mounts, but not properly, and I get home home/home as file systems. And after an 'exit', it still complains about the lack of /export/home/udippel. % zpool import and % zpool list are as expected, though. How can I now teach it to come up properly as /export/home/udippel, please ? Uwe This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
