Login or Register to Ask a Question and Join Our Community


Red Hat

Memory problems in NFS client server

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Memory problems in NFS client server
Prev   Next
# 1  
Old 05-02-2012
Memory problems in NFS client server
Hi all,

i have some doubts in a situation that i fail to get an answer in Google.

I have a solaris 10 nfs server and 5 centos 6.0 nfs clients.

The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the nfs mount point. I can see also that the speed that the memory is "disappearing" is related to the use of the nfs fs (3 of the 5 servers use the nfs fs more intensively and in those it disappears faster).

I m mounting with:
rw,vers=4,hard,rsize=32768,wsize=32768,noac

Kernel version:2.6.32-71.el6.x86_64 and 2.6.32-220.13.1.el6.x86_64 (i have updated in one server to check the behavior and its the same)

and:

rpm -aq | grep -i nfs
nfs-utils-1.2.2-7.el6.x86_64
nfs4-acl-tools-0.3.3-5.el6.x86_64
nfs-utils-lib-1.1.5-1.el6.x86_64

and in the updated server
nfs4-acl-tools-0.3.3-5.el6.x86_64
nfs-utils-lib-1.1.5-4.el6.x86_64
nfs-utils-1.2.3-15.el6.x86_64

By the way i m checking the memory with the free -m command in this line:
...
-/+ buffers/cache: 480 3286
...
(i did a umount/mount some time ago so now its not bad, but in couple of days it gets the opposite or worse..)


Can someone give me some lights about this behavior?

Thanks
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies

2. AIX

AIX NFS Server and NFS Client

Hi 2 ALL, try to run NFS Server in AIX 7.1 : 1. Step by step on NFS Server node mkdir /tmp/test chgrp staff /tmp/test chmod 775 /tmp/test-- create export directory (fs) mknfsexp -d /tmp/test -t ro exportfs -va show mount -e :/# exportfs -av exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies

3. Red Hat

Unable to access NFS share on Solaris Server from Linux client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. share -F nfs -o rw /var/share & then ran the following svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies

4. Solaris

Can't access NFS Share on Solaris Server from a Linux Client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. & then ran the following On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies

5. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

6. Solaris

Solaris 9 as a nfs client -- centos as a nfs server.

Hello, I have a centos as nfs server, its name is centos_A. After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/* But, My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies

7. UNIX for Advanced & Expert Users

Determining IP address of NFS server on client

Hi. We use an Isilon cluster system to provide our NAS. The Isilon uses a round-robin DNS setup to spread mount requests across the many nodes of the cluster. When a node needs work, the filesystems that are mounted to it need to be moved to other nodes prior to shutting the node down. I... (2 Replies)
Discussion started by: rascalrick
2 Replies

8. Programming

tcp server listening, client connecting problems

hello everyone. I tried searching for something related to this, but I figured it was time to ask my own question. I am experiencing these problems using Ubuntu 7.04 I am starting up a TCP listener/server and once connected, will act as a communication/control link with a program on another... (3 Replies)
Discussion started by: pjwhite
3 Replies

9. Linux

NFS Server FC7 Solaris client problems!

Hi, my problem is that I am not able to grand the nfs directory on a Fedora 7 server to a standard solaris client. I always got the messages no permission. Important: No change on the client (Solaris) is possible! So I am not able to change the NFS Version on the client side to force the... (3 Replies)
Discussion started by: joerg
3 Replies

10. UNIX for Advanced & Expert Users

NFS server problems [merged]

I have a machine A NFS mounted on machine B I am doing a build from machine B on the MFS mounted dir of machine A but I keep getting the following: NFS server A not responding still trying. I go to machine A and can log onto machine A and everything seems fine. How do I go about finding... (6 Replies)
Discussion started by: brv
6 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

nfs

nfs(7)							 Miscellaneous Information Manual						    nfs(7)

NAME

       nfs, NFS - network file system

DESCRIPTION

       The  Network File System (NFS) allows a client node to perform transparent file access over the network.  By using NFS, a client node oper-
       ates on files residing on a variety of servers and server architectures, and across a variety of operating systems.  File access  calls	on
       the  client  (such  as  read  requests)	are converted to NFS protocol requests and sent to the server system over the network.	The server
       receives the request, performs the actual file system operation, and sends a response back to the client.

       NFS operates in a stateless manner using remote procedure calls (RPC) built on top of an external data representation (XDR) protocol.   The
       RPC protocol enables version and authentication parameters to be exchanged for security over the network.

       A server grants access to a specific file system to clients by adding an entry for that file system to the server's file.

       A  client  gains access to that file system using the command to request a file handle for the file system (see mount(1M)).  (A file handle
       is the means by which NFS identifies remote files.)  Once a client mounts the file system, the server issues a file handle  to  the  client
       for  each  file	(or directory) the client accesses.  If the file is removed on the server side, the file handle becomes stale (dissociated
       with a known file), and the server returns an error with set to

       A server can also be a client with respect to file systems it has mounted over the network; however, its  clients  cannot  directly  access
       those  file systems.  If a client attempts to mount a file system for which the server is an NFS client, the server returns with set to The
       client must mount the file system directly from the server on which the file system resides.

       The user ID and group ID mappings must be the same between client and server.  However, the server maps UID 0 (the  superuser)  to  UID	-2
       before performing access checks for a client.  This process prevents gaining superuser privileges on remote file systems.

RETURN VALUE

       Generally,  physical  disk I/O errors detected at the server are returned to the client for action.  If the server is down or inaccessible,
       the client receives the message:

       where is the hostname of the NFS server.  The client continues resending the request until it receives an acknowledgement from the  server.
       Therefore,  the	server	can  crash  or power down, and come back up without any special action required by the client.	The client process
       requesting the I/O will block, but remains sensitive to signals (unless mounted with the option) until the server  recovers.   However,	if
       mounted with the option, the client process returns an error instead of waiting indefinitely.

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       exportfs(1M), share(1M), mount(1M), mount_nfs(1M), nfsd(1M), mount(2), fstab(4), dfstab(4).

																	    nfs(7)