No, you are not quite getting it.
let's say your root drives were design like this
d0 main mirror for /
d10 - submirror c0t0d0
d20 - submirror c0t1d0
you would detach d20 from d0. leaving you with a single sided mirror that is made up of d10 attached to d0.
using d20 you would use this disk...
I guess the best thing is to get back to your issue.
I had the same problem as you with a system I inherited from another group that we took over their server support. Fortunately for me it was /var that needed to be grown, so I just used growfs. Unfortunate for you /usr is one of only a few...
what Sun part number are they?
2 CPU's per board?
Are you sure you have the dimms on the correct place. depending on the memory configuration they need to be in specific places on the CPU board
So whats your question?
depending if you are working on sparc or x86 running Solaris you will get different responses.
On sparc, an init 0 will take you to the OBP prompt. I'm guessing the shutdown -i0 will also. I never use the shutdown command.
I use the init commands so it will cleanly...
Your request does not make any sense.
142901-12 is a kernel patch, pretty recent in fact.
119255-73 is a "install and patch utility" patch. They are not the same.
why do you need to remove the latest kernel patch?
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
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.
example:
mirror d10
c0t0d0s0 d11
c0t1d0s0 d12
you run stmsboot -e (sparc only)
for x64/x86, you modify the file...
actually I was mistaking, it is /, /usr and swap that *should not* be grown.
http://docs.sun.com/app/docs/doc/802-2422/6i6cubkeo?l=en&a=view
because of these limitations, this is a good reason for migrating to ZFS.
you can not grow /var or / even with growfs. all other filesystems growfs is a viable solution as KenCunningham stated. I've used it many times in the past.
Since you said it can not find it, it leads me to believe right now you are attempting to setup the concat?
you can not just modify it.
you have to delete it and recreate it.
How did you get the d50 created in the first place. it will not create metadevice if a physical path is non-existent...
You should use:
If you have not broken the mirrors already for root and var in your original BE this will work. If you have already broke them then it will not.
lucreate -c orig -n patchBE -m /:/dev/md/dsk/d0:ufs,mirror -m /:/dev/md/dsk/d12:detach,attach,preserve -m...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.