06-27-2007
Offtopic : Few months ago I posted here some thoughts on NFS performance version 3. There are some issues with NFS clients and server on Linux, whereas UNIX's times look good. It's preferable that you use version 4, as it has many improvements, of course, if you are looking for better performance.
9 More Discussions You Might Find Interesting
1. SCO
I am very new to Unix. Is it possible to setup a NFS share on a Sco Unix server that could be accessable by a Windows 2003 server? If so could someone point me in the right direction with either the commands or documentation? (1 Reply)
Discussion started by: Johnd
1 Replies
2. Solaris
:confused:Hi all
When i see in the /var/adm/messages, i saw the following error
unix: NFS write error on host : Stale NFS file handle.
unix: (file handle: 45ca415 3e7 a0000 2c7f6 3ebfc25f a0000 2 3e49)
It is using sunOS 5.7. Is anybody know what is this error?
Is is related to any network... (2 Replies)
Discussion started by: AirWalker83
2 Replies
3. Linux
Hello All,
I have a small question regarding the NFS file handles.
Suppose I have a NFS client who has requested for a particular file from the NFS server.Now lets assume that I am using a NFS v2 server. So I get the filehandle for that file and I can use it. Suppose later I upgrade the server to... (0 Replies)
Discussion started by: prathamesh
0 Replies
4. HP-UX
I am new in UNIX so pardon me if I am asking this question. We are using SFU in Windows to have a Windows folder mounted over UNIX. While we can see the mount, everytime i cd on the mounted folder (e.g. cd CONFIG) I always get Permission denies error. Does anyone know why I cannot go inside the... (11 Replies)
Discussion started by: Jolas
11 Replies
5. Solaris
Ok. Here is the situation, I have server A which need to access /tmp folder of server B. Can I mount NFS share (/tmp) from client (serverA)?please let me know (3 Replies)
Discussion started by: sam101
3 Replies
6. Solaris
How do I get directories form remote server " A " mounted to server B? Please provide the necessary steps. (1 Reply)
Discussion started by: sam101
1 Replies
7. Solaris
Hello,
I have a quick question. How do you know which protocol version of NFS is setup on your Solaris 10 servers?
Example 2, 3 or 4 (3 Replies)
Discussion started by: bitlord
3 Replies
8. UNIX for Dummies Questions & Answers
I have a somewhat interesting problem, we've decided to load balance a java application and as such I'll be running our application on four physical machines as opposed to the single machine it's currently running on.
I've centralized the directory that the application requires (including the... (2 Replies)
Discussion started by: xdawg
2 Replies
9. Solaris
Oct 13 12:19:15 xyz nfs: NFS write error on host xyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: (file handle: 68000000 1bc5492e 20000000 377c5e 1ce9395c 720a6203 40000000 bdfb0400)
Oct 13 12:19:15 xyz nfs: NFS write error on host zyz: Stale NFS file handle.
Oct 13 12:19:15 xyz nfs: ... (5 Replies)
Discussion started by: psychocandy
5 Replies
nfsiod(8) System Manager's Manual nfsiod(8)
NAME
nfsiod, biod - The local NFS compatible asynchronous I/O daemon
SYNOPSIS
nfsiod [ numthreads ]
DESCRIPTION
The nfsiod daemon runs on an NFS compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
server. The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread. If none is
available, the process itself issues the request to the server and waits for the reply.
The optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for most
systems.
When reading, if the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
the process is currently requesting. If the readahead completes before the process asks for that block, then the subsequent read system
call for that data completes immediately and does not have to wait for the NFS request to complete. Read ahead will be triggered again so
the read may find that next block available as well.
When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the process. If
the process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
has to handle a NFS write itself. This means the process has to wait until the server finishes the write. For Tru64 UNIX servers, the NFS
block size is 8Kb and UFS tries to cluster I/O 64Kbs at a time. If the client is running with 7 I/O threads, 8 write requests can be in
progress at once. This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.
Unlike nfsd, each client thread can use either UDP or TCP. However, if TCP mounts are active, the nfsiod process will time out, close idle
TCP connections, and acknowledge any connections closed by the server.
The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos). Because I/O
to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.
The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process. The ps axml command displays
idle I/O threads under PID 0. Idle threads will be waiting on nfsiod_wait. Therefore, if 7 I/O threads are configured, only 1 nfsiod
process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.
FILES
Specifies the command path Specifies the file for logging NFS activity.
RELATED INFORMATION
Commands: nfsd(8), nfsstat(8)
Daemons: async_daemon(2) delim off
nfsiod(8)