Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here




Hello Forumers,

any thoughts on this:

Assume someone took the disks / LUNs under control of SVM. STMS is not active therefore the boot volume might be called: /dev/(r)dsk/c1t0d0 and some FC attached LUN (2 paths)  may appear as: /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0.

The file /etc/vfstab would of course refer to objects such as /dev/md/(r)dsk/d20 or similar. Using command metastat would allow to show the association between /dev/md/(r)dsk/dN and /dev/(r)dsk/c1t0d0 and /dev/(r)dsk/c2t5WWNNd0 or /dev/(r)dsk/c3t5WWNNd0, respectively.

Now the admin would decide to enable STMS, so the boot volume might suddenly appear as:  /dev/(r)dsk/c4t2000000....d0 and instead of two the two /dev/(r)dsk/c2t5WWNNd0 and /dev/(r)dsk/c3t5WWNNd0 (from above) one would only see a STMS metadevice , i.e. c4t6.....d0.

Would SVM recognize this modification automatically (as the  respective device / metadevice association from above would cease to exist)? Or is there the need for explicit activity, and if so: what?

Thanks. Cheers dj600stoxx
Replies continue below

Recommended for you


If you are asking: if you are using SVM for your root devices, and then you enable stms, will the underlying devices change that make up the metadevice. The answer is yes.


mirror d10
c0t0d0s0 d11
c0t1d0s0 d12

you run stmsboot -e (sparc only)
for x64/x86, you modify the file /kernel/drv/fp.conf, you don't use stmsboot command.

it will become:

mirror d10
WWNd0 d11
WWNd0 d12

You can after that fact (after you complete the stms reboot as required) run the following command to see the correlation between the need id and the old.

stmsboot -L

non-STMS device name                    STMS device name


/dev/rdsk/c0t0d0    /dev/rdsk/c4t500000E06745DEE0d0

/dev/rdsk/c0t1d0    /dev/rdsk/c4t500000E07868A070d0



Thank you so much djr111, you answered my question. Does this what you said also apply for non-boot disks that are under SVM control first and that are in addition taken under control of STMS afterwards?

Seems that with SAN 4.4 there is a need for special handling but maybe in Solaris 10 this is also done automatically?


Arrays are sometimes different, you may need to supply special information/configurations to get mpxio working. the only time this is probably not true is on sun arrays, they are configured to work already in solaris

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close