Henrik Johansson wrote:
...
> zpool create ollespappa c4t6006157000028797091143454C304238d0s2 \
> c4t6006157000028797091143454C305240d0s2 \
> c4t6006157000028797091143454C309323d0s2
> 
> With the LUN id I only need to look at the disk part, which is quite a  
> bit easier:
> 
> zpool create ollespappa c3t5006157452A6A768d387s2 \
> c3t5006157452A6A768d230s2 c3t5006157452A6A768d123s2
> 
> Do we have to live with this when if we switch to MPxIO?

Yes, you do - that's because of the way we handle the
device names when MPxIO is turned on.

As long as you haven't run "devfsadm -C" or "reboot -- -r" then
you should, however, be able to run "stmsboot -L" to see what
the MPxIO to non-MPxIO device mapping is.

You could even create your zpools with MPxIO disabled,
and then turn on MPxIO afterwards. ZFS will import your
pools and run with them just fine.


James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp       http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to