memory_affinity

[gatetec]

How do you update memory_affinity?
I am getting errors show below.

thx much

TOC # vmo -o memory_affinity=0
vmo: 1485-115 Tunable memory_affinity is of type B and cannot be changed without
-r
root@rtprod1:/>
TOC # vmo -o -r memory_affinity=0
vmo: 1485-110 Invalid tunable name -r
Usage: vmo -h [tunable] | {-L [tunable]} | {-x [tunable]}
vmo [-p|-r] (-a | {-o tunable})
vmo [-p|-r] (-D | ({-d tunable} {-o tunable=value}))
root@rtprod1:/>
TOC # vmo -r memory_affinity=0
vmo: 1485-104 -r|-p are not allowed before -h, -L, -x, or alone
Usage: vmo -h [tunable] | {-L [tunable]} | {-x [tunable]}
vmo [-p|-r] (-a | {-o tunable})
vmo [-p|-r] (-D | ({-d tunable} {-o tunable=value}))

 

[sjm2]

Did you try "vmo -r -o memory_affinity=0"?

 

[gatetec]

Yes, it works.

Setting memory_affinity to 0 in nextboot file
Warning: some changes will take effect only after a bosboot and a reboot
Run bosboot now? n
Warning: changes will take effect only at next reboot

I can't reboot the node as to it is in use.
My concern is bosboot. Should it take effect and take care of bosboot if I reboot later?

thx much

 

[DukeSSD]

FFS gatetec,

You must be an AIX admin or you wouldn't be running vmo.

It tells you to add -r, you guess, fair enough, and it tells you the syntax:

vmo [-p|-r] (-a | {-o tunable})

So you type
vmo -r {miss out the obviously required -o} tunable
and ask for more help when the command fails.

When you run it with {the obviously required -o} it tells you:
Warning: some changes will take effect only after a --> "BOSBOOT" <-- and a reboot

So you decide not to run bosboot:
"Run bosboot now? n"

Why you answered no I cannot imagine.

Then you ask if it will some how 'magically' run bosboot when you next reboot.

NO!

Read the man pages, read the command reference, read what is on the BL**DY screen!

Run bosboot for the changes to be applied after reboot.
As the bosboot is REQUIRED and you have not run it, if the system fails, crashes, has a power outage, before you run bosboot then your system is at risk of being left in a strange state after reboot and it may not boot, ever again!

If a command says you need to run bosboot and gives you the option to do it, FFS DO IT, there and then, DO NOT WAIT.

You now have a system that NEEDS to recreate the BLV before it is rebooted and you NEVER know when the next reboot will be!

The command ref for vmo, 5.2 and 5.3 - you never said what version and it was not available before 5.2:

http://publib.boulder.ibm.com/infoc...?topic=/com.ibm.aix.cmds/doc/aixcmds6/vmo.htm

Says, quite clearly:

-r When used in combination with -o, -d or -D, makes changes apply to reboot values, for example, turns on the updating of the /etc/tunables/nextboot file. If any parameter of type Bosboot is changed, the user will be prompted to run bosboot

Well you were prompted and you declined the offer.

You MUST run bosboot to all rootvg bootable disks ASAP, no need to reboot, just run the command. Then if there is an unexpected reboot, or you get the chance to reboot, your system should be safe.

Please read the screen, the man pages and the command reference before you post again.

We are here to help you with problems but we are not here to read the man pages or do your job for you.

 

[mrn]

LOL

Now look what you've done gatetec ; it'll take weeks for him to calm down now.......

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."

 

[DukeSSD]

Had my RTFM hat on at the time.

Nice and calm now...

 

[p5wizard]

And Duke, there's no real harm done in this case. If there's an absolute requirement to run bosboot (e.g. after installation of new drivers, SP's, TL's) the system will run the bosboot without first verifying if that is what you want to do.

If however, you're modifying more than one vmo parameter that each requires a bosboot update to have effect, it's kind of silly to run the bosboot again and again after each modification.

So, gatetec, just run the command once again and answer y to the bosboot question this time. running bosboot just refreshes/updates your Boot LV so that the system is prepared for next boot. It won't affect your running system. But after the bosboot (now) and the reboot (some time in the future) all your vmo changes will come into effect.



HTH,

p5wizard