kernel parameter changes

[Gurumanickam]

hi all,

Yesterday i got a error "vmunix: file: table is full" in my syslog. i think this error is because of number of file opened at a time is crossed the limit specified in kernel parameter nfile. i discussed with the technical consultant they have given the follwing setting.

The value of nfile kernel parameter should be (15 * NPROC + 2048) where NPROC is maximum number of processes which should be a4096.


whether the above value is recommended or what value i can set. please suggest, replies are highly apprciated.

my systems kernel parameter value as below

Parameter Current Dyn Planned Module Version
===============================================================================
NSTRBLKSCHED - - 2
NSTREVENT 50 - 50
NSTRPUSH 16 - 16
NSTRSCHED 0 - 0
STRCTLSZ 1024 - 1024
STRMSGSZ 65535 - 65535
acctresume 4 - 4
acctsuspend 2 - 2
aio_listio_max 256 - 256
aio_max_ops 2048 - 2048
aio_physmem_pct 10 - 10
aio_prio_delta_max 20 - 20
allocate_fs_swapmap 0 - 0
alwaysdump 1 - 1
bootspinlocks - - 256
bufcache_hash_locks 128 - 128
bufpages 0 - (NBUF*2)
chanq_hash_locks 256 - 256
core_addshmem_read 0 Y 0
core_addshmem_write 0 Y 0
create_fastlinks 0 - 0
dbc_max_pct 50 - 50
dbc_min_pct 5 - 5
default_disk_ir 0 - 0
desfree - - 0
disksort_seconds 0 - 0
dmp_rootdev_is_vol 0 - 0
dmp_swapdev_is_vol 0 - 0
dnlc_hash_locks 512 - 512
dontdump 0 - 0
dskless_node - - 0
dst 1 - 1
effective_maxpid - - ((NPROC<=30000)?30000:(NPROC*5/4))
eisa_io_estimate - - 0x300
enable_idds 0 - 0
eqmemsize 15 - 15
executable_stack 1 - 1
fcp_large_config 0 - 0
file_pad - - 10
fs_async 0 - 0
ftable_hash_locks 64 - 64
hdlpreg_hash_locks 128 - 128
hfs_max_ra_blocks 8 - 8
hfs_max_revra_blocks 8 - 8
hfs_ra_per_disk 64 - 64
hfs_revra_per_disk 64 - 64
hp_hfs_mtra_enabled 1 - 1
hpux_aes_override - - 0
initmodmax 50 - 50
io_ports_hash_locks 64 - 64
iomemsize - - 40000
ksi_alloc_max 4256 - (NPROC*8)
ksi_send_max 32 - 32
lotsfree - - 0
max_async_ports 50 - 50
max_fcp_reqs 512 - 512
max_mem_window 0 - 0
max_thread_proc 256 - 256
maxdsiz 1073741824 - 1073741824
maxdsiz_64bit 1610613009 - 1610613009
maxfiles 60 - 60
maxfiles_lim 1024 Y 1024
maxqueuetime - - 0
maxssiz 261244008 - 261244008
maxssiz_64bit 261244008 - 261244008
maxswapchunks 2048 - 2048
maxtsiz 1073741824 Y 1073741824
maxtsiz_64bit 1610612736 Y 1610612736
maxuprc 75 Y 75
maxusers 64 - 64
maxvgs 10 - 10
mesg 1 - 1
minfree - - 0
modstrmax 500 - 500
msgmap 42 - (2+MSGTQL)
msgmax 8192 Y 8192
msgmnb 16384 Y 16384
msgmni 50 - 50
msgseg 2048 - 2048
msgssz 8 - 8
msgtql 40 - 40
nbuf 0 - 0
ncallout 963 - (16+NKTHREAD)
ncdnode 150 - 150
nclist 1124 - (100+16*MAXUSERS)
ncsize 5884 - (NINODE+VX_NCSIZE)+(8*DNLC_HASH_LOCKS)
ndilbuffers 30 - 30
netisr_priority - - -1
netmemmax - - 0
nfile 1371 - (16*(NPROC+16+MAXUSERS)/10+32+2*(NPTY+NSTRPTY+
NSTRTEL))
nflocks 200 - 200
nhtbl_scale 0 - 0
ninode 764 - ((NPROC+16+MAXUSERS)+32+(2*NPTY))
nkthread 947 - (((NPROC*7)/4)+16)
nni - - 2
no_lvm_disks 0 - 0
nproc 532 - (20+8*MAXUSERS)
npty 60 - 60
nstrpty 60 - 60
nstrtel 60 - 60
nswapdev 10 - 10
nswapfs 10 - 10
nsysmap 800 - ((NPROC)>800?2*(NPROC):800)
nsysmap64 800 - ((NPROC)>800?2*(NPROC):800)
o_sync_is_o_dsync 0 - 0
page_text_to_local - - 0
pfdat_hash_locks 128 - 128
public_shlibs 1 - 1
region_hash_locks 128 - 128
remote_nfs_swap 0 - 0
rtsched_numpri 32 - 32
scroll_lines 100 - 100
scsi_max_qdepth 8 Y 8
scsi_maxphys 1048576 - 1048576
sema 1 - 1
semaem 16384 - 16384
semmap 202 - (SEMMNI+2)
semmni 200 - 200
semmns 5000 - 5000
semmnu 30 - 30
semmsl 2048 Y 2048
semume 10 - 10
semvmx 32767 - 32767
sendfile_max 0 - 0
shmem 1 - 1
shmmax 0x5dc00000 Y 0X5DC00000
shmmni 200 - 200
shmseg 120 Y 120
st_ats_enabled 0 - 0
st_fail_overruns 0 - 0
st_large_recs 0 - 0
st_san_safe 0 - 0
streampipes 0 - 0
swapmem_on 1 - 1
swchunk 2048 - 2048
sysv_hash_locks 128 - 128
tcphashsz 0 - 0
timeslice 10 - (100/10)
timezone 420 - 420
unlockable_mem 0 - 0
vas_hash_locks 128 - 128
vnode_cd_hash_locks 128 - 128
vnode_hash_locks 128 - 128
vol_checkpt_default 10240 - 10240
vol_dcm_replay_size 262144 - (256*1024)
vol_default_iodelay 50 - 50
vol_fmr_logsz 4 - 4
vol_max_bchain 32 - 32
vol_max_nconfigs 20 - 20
vol_max_nlogs 20 - 20
vol_max_nmpool_sz 4194304 - (4*1024*1024)
vol_max_prm_dgs 1024 - 1024
vol_max_rdback_sz 4194304 - (4*1024*1024)
vol_max_vol 8388608 - (8*1024*1024)
vol_maxio 256 - 256
vol_maxioctl 32768 - 32768
vol_maxkiocount 2048 - 2048
vol_maxparallelio 256 - 256
vol_maxspecialio 256 - 256
vol_maxstablebufsize 256 - 256
vol_min_lowmem_sz 524288 - (512*1024)
vol_mvr_maxround 256 - 256
vol_nm_hb_timeout 10 - (10)
vol_subdisk_num 4096 - 4096
vol_vvr_transport 1 - (1)
vol_vvr_use_nat 0 - (0)
volcvm_cluster_size 16 - 16
volcvm_smartsync 1 - 1
voldrl_max_drtregs 2048 - 2048
voldrl_min_regionsz 512 - 512
voliomem_chunk_size 65536 - (64*1024)
voliomem_maxpool_sz 4194304 - (4*1024*1024)
voliot_errbuf_dflt 16384 - 16384
voliot_iobuf_default 8192 - 8192
voliot_iobuf_limit 131072 - 131072
voliot_iobuf_max 65536 - 65536
voliot_max_open 32 - 32
volraid_rsrtransmax 1 - 1
vps_ceiling 16 - 16
vps_chatr_ceiling 1048576 - 1048576
vps_pagesize 4 - 4
vx_fancyra_enable 0 - 0
vx_maxlink 32767 - 32767
vx_ncsize 1024 - 1024
vx_ninode 0 - 0
vxfs_max_ra_kbytes 1024 - 1024
vxfs_ra_per_disk 1024 - 1024
vxtask_max_monitors 32 - 32

[Raj D.]

Gurumanickam,

You need to check the system file usage,

You can paste the output of:

# sar -v 4 4

# glance -t

Also you can check if nflock and nfiles kernel parameters are falling short, then you need to increase these parameters,

Cheers,
Raj.

[Raj D.]

Remember to see file-sz in the sar -v output and look for nflocks in glance -t output,

Also remeber changing this parameter need a reboot to include the nw values into the kernel,

Cheers,
Raj.

[Gurumanickam]

i already checked by sar -v here is the o/p

16:39:24 text-sz ov proc-sz ov inod-sz ov file-sz ov
16:39:26 N/A N/A 199/532 0 764/764 0 1326/1381 0
16:39:28 N/A N/A 199/532 0 764/764 0 1324/1381 0
16:39:30 N/A N/A 199/532 0 764/764 0 1324/1381 0
16:39:32 N/A N/A 199/532 0 764/764 0 1327/1381 0
16:39:34 N/A N/A 199/532 0 764/764 0 1327/1381 0

[Raj D.]

From the output I can see the ninode and nfile value are reaching 100%,
- also you need to check nflocks values from glance -t, and plan to increase these vlaues,

cheers,
Raj.

[Gurumanickam]

glance software is expired in my system. i'm not able to check with glance -t

[Yogeeraj_1]

hi,

to start with, i would recommend that you increase your nproc value.

This will definitely impact on several other kernel parameters.

On our system, it has the fixed value of 4096 instead of the formula ((20+8*MAXUSERS))


Hope this helps!

kind regards
yogeeraj

[Raj D.]

Your system has defined with a low file lock value ( nflocks 200 - 200 ), and need to increase you can increase nflocks to 150% , and check further.



Also see check this link:
http://66.34.90.71/ITRCForumsEtiquette/after.html

hth,
Raj.

[Gurumanickam]

pl. suggest how much i can increase nprc

[Raj D.]

Gurumanickam,

From the output you can see mainly nproc isnt getting over , its value showing 199/532 (used/total_available , 3rd column), the parameter is getting full is nfile, and ninode you can plan to increase all by 100 - 150 % , ( nfile, ninode , nflocks and take nproc as well),


good luck,
Raj.

[Gurumanickam]

In planned coloumn there is a formula. is it required to apply it. if i am not applying will it affect my system or software performance.

[Raj D.]

Gurumanickam,
Also have a look on the below links,


http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1055201&admit=-682735245+1170504312600+28353475

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=28069&admit=-682735245+1170504422461+28353475

hth,
Raj.

[Raj D. · Accepted solution]

Not necessarily ,similiarly you can use command prompt to change this vlaues with kmtune,

close all applications, performthe kernel tuning and reboot, remember you need to reboot to incorporate the change into the kernel,

Ex: # kmtune -s nfile=2000
# kmtune -s nflocks=500
# kmtune -s ninode=1024
# kmtune -s maxfiles=150
# kmtune -s nproc=800

# ./mk_kernel
# ./kmupdate
# shutdown -r -y 0

After reboot check the values, and also check the usage it should look good.

Goodluck,
Raj.

[Yogeeraj_1]

hi again,

if you are not at ease with the command line, it would be preferable to use SAM to make the changes.

good luck!

kind regards
yogeeraj

[Bill Hassell]

DO not use formulas -- they are never right. Your value for NFILE is way too small. Change it to 4096 and you'll be fine for now. The sar -v 1 reading will give you only 2 useful parameters: NFILE and NPROC. The first number in each pair is current and the second is maximum. Since your maximum is is just barely above the current value, you will have lots of problems.