setting maxdsiz to unlimited

[John Ben Urban]

In July my HP machine had maxdsiz (as reported by ulimit) set to unlimited.

$ uname -a
HP-UX njtest01 B.11.11 U 9000/800 137901517 unlimited-user license
$ sh ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
$ date
Thu Jul 10 14:12:58 EDT 2003
$

My team of system admins have made various changes to the OS and various rebooted. The ulimit for data now reports:

$ uname -a
HP-UX njtest01 B.11.11 U 9000/800 137901517 unlimited-user license
njtest01 $ sh ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4293279744
stack(kbytes) 8192
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 4096
$ who -b
. system boot Jul 24 12:57
$ /usr/sbin/kmtune | grep maxdsi
maxdsiz 0x99000000 - 0X99000000
maxdsiz_64bit 0x400000000 - 0X400000000
$ /etc/sysdef | grep maxd
maxdsiz 626688 - 0-503866 Pages -
maxdsiz_64bit 4194304 - 1024-1073479679 Pages -
$

Does anyone know how to get 'data' back to "unlimited" ?

[John Bolene]

that value is pretty much unlimited

way larger than you will ever use

[Elena Leontieva · Accepted solution]

See this link:

http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000068695479

Document description: ulimit displays wrong value for data field
Document id: KBRC00012516

[Steven E. Protter]

I'd set it high, but not unlimited.

I had problmes with my system when I had it unlimited and was forced to change it to a high number instead.

SEP

[Todd McDaniel_1]

On my 48way Superdome, I have the following setup...71.2GB memory...
__________________________________________
# kmtune -q maxdsiz_64bit
Parameter Current Dyn Planned Module Version
===============================================================================
maxdsiz_64bit 0x50000000 - 0X50000000

# kmtune -q maxdsiz
Parameter Current Dyn Planned Module Version
===============================================================================
maxdsiz 0x50000000 - 0X50000000

__________________________________________
nfiles/nproc/nfile are as follows...
HP-UX chpcfas1 B.11.11 U 9000/800 09/15/03

13:21:49 text-sz ov proc-sz ov inod-sz ov file-sz ov
13:21:54 N/A N/A 1960/30000 0 5275/37332 0 53253/85010 0
13:21:59 N/A N/A 1959/30000 0 5271/37332 0 53240/85010 0
13:22:04 N/A N/A 1955/30000 0 5265/37332 0 53210/85010 0
13:22:09 N/A N/A 1954/30000 0 5262/37332 0 53146/85010 0
13:22:14 N/A N/A 1955/30000 0 5266/37332 0 53211/85010 0

[Todd McDaniel_1]

Sorry forgot to add my notes to above post...

I can't ever conceive of having to increase it... and mine is pretty high already.

[John Ben Urban]

I do not want to use the value of: data(kbytes) 4293279744 but I want data to report unlimited just like memory and file does. Does anyone know what to change to make it report unlimited and not report a big number.

[Todd McDaniel_1]

Very confusing John, hehe... you have 2 posts with the same question, no matter. It appears that you have found the reason for the problem of using "unlimited" value for maxdsiz* kernel parms...

______________________________
I dont know your setup, but I would still like to see you reduce the value to a lower number...say 0x50000000,and see how your system runs. THEN, if you dont like that setting, maybe then increase it back and see if you get the unlimited value....

However, IMHO, It is not likely you will ever reach that value for maxdsi*, even with a large amount of memory, as you would probably run out of other resources first.


_______________________________
If you must have the "unlimited" value, I would contact HP directly and ask about that issue, It may not be resolved till a future patch...