10-02-2010
Could you let me know how to increase those? Thanks in advance!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
tar: Memory allocation failed for extended data while reading : Not enough space
what can be done for the above problem?
top utility reports memory usage as follows:
Memory: Real: 2688M/15G act/tot Virtual: 1492M/42915M use/tot Free: 11G
this cannot be a disk space problem as we have... (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies
2. Programming
I am trying to compile the pro*C file but gives errors. It says it encountered "std" while it was expecting ; , = ( $ $ORACLE_HOME/bin/proc tradewind/dataaccess/Blob.pcc
Pro*C/C++: Release 10.2.0.3.0 - Production on Fri May 9 11:10:54 2008
Copyright (c) 1982, 2005, Oracle. All rights... (0 Replies)
Discussion started by: shafi2all
0 Replies
3. UNIX for Advanced & Expert Users
In our directory there are too many files, & if I try to execute mv *.gz or rm *.l command it fails, providing error string as - 'arg list too long'. This doesnt happen always, is there any way we know, limit on the rm & mv command so we can take care of this failure in future executions ? (9 Replies)
Discussion started by: videsh77
9 Replies
4. AIX
Hi All,
I have a process running on my AIX 5.3 server box. The process runs fine for 5-6days but then crashes. The log file shows malloc failure and the svmon (Virtual memory size), ps -lef (SZ value) are also gradually increasing. But unfortunately MALLOCDEBUG and any other memory debugging... (3 Replies)
Discussion started by: SBatra
3 Replies
5. SuSE
Hi,
My program was running for a whole night. after 12 hours i got an error message "Cannot allocate memory" during the shmat commmand. So can you please let me know what could be the reason? is there any solution?
thanks in advance.
Regards,
Mano (5 Replies)
Discussion started by: ManoharanMani
5 Replies
6. SuSE
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
7. Linux
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
8. Linux
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
9. Red Hat
Hi ,
Our one of VMguest all lvm got unmounted once the machine is rebooted
when in repair state dmesg its showing an error out of memory killed process 22289 (lvm)
please refer screen shots attached
when i look the lvscan its showing all lvm are inactive
i checked throuh top there... (0 Replies)
Discussion started by: venikathir
0 Replies
LEARN ABOUT HPUX
nfs3_max_transfer_size
nfs3_max_transfer_size(5) File Formats Manual nfs3_max_transfer_size(5)
NAME
nfs3_max_transfer_size - control the data portion size of a NFS version 3 read, write, readdir, or readdirplus request
VALUES
Failsafe
Default
Allowed values
Recommended values
A warning will be issued at runtime if the tunable is set to a value greater than 1048576 since this is outside the tested limits. This is
not a serious warning but just an information message for the administrator.
DESCRIPTION
controls the maximum size of the data portion of a NFS version 3 read, write, readdir, or readdirplus request. This parameter controls both
the maximum size of a request that the server returns as well as the maximum size of a request that the client generates.
Who Is Expected to Change This Tunable?
Distributed file system administrators should examine this value if they want to decrease or increase the default size of a NFS packet.
Restrictions on Changing
The tunable is dynamic; however, the transfer size for a file system is set when the file system is mounted. To affect a particular file
system, unmount and mount the file system after changing this parameter.
The actual NFS version 3 transfer size is controlled by these tunable parameters: and The actual transfer size will depend on the tunable
with the smallest value. For NFS version 3 TCP traffic increase and to the same value to increase the transfer size. To decrease the trans-
fer size, just changing is sufficient.
When Should the Value of This Tunable Be Raised?
An increase in the transfer size will result in fewer requests to the NFS server at the expense of system resources on both the NFS client
and NFS server.
What Are the Side Effects of Raising the Value?
Setting the limit too large might result in errors from UDP and communication problems between the client and the server.
When Should the Value of This Tunable Be Lowered?
In the event of NFS communication failures, the value should be changed back to the default value.
What Are the Side Effects of Lowering the Value?
An increase in NFS version 3 network traffic caused by an increase in the number of I/O requests.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
kctune(1M), sam(1M), gettune(2), settune(2), nfs3_bsize(5), nfs3_max_transfer_size_cots(5), values(5).
Tunable Kernel Parameters nfs3_max_transfer_size(5)