06-12-2015
There are only so many components involved, so the debugging should be straightforward:
How is the NAS connected to your system? I suppose it is an NFS-mount, no?
If so, the following has to be checked:
- network equipment: scp a larger file somewhere to test. Measure time.
- name resolution: put NAS server into /etc/hosts and have local files (=/etc/hosts) take precedence over DNS in /etc/resolv.conf
- mount options: look carefully how the FS from the NAS is mounted. Typical problems include CIO (concurrent I/O), user authentication via outside sources (i.e. user authorization via Kerberos and a slow, unresponsive Kerberos server) and the like.
- If you use NFSv4 (you shouldn't - it is crap) check the NFS-domain. It has to be set on every client and server.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello Guru,
I am using a Pro*C program to prepare some reports
usaually the report file size is greater than 1GB.
But nowadays program is very slow.
I found out the program is taking much time to write data to file .....
is there any unix related reason to be slow down, the file writting... (2 Replies)
Discussion started by: bhagyaraj.p
2 Replies
2. Shell Programming and Scripting
Hi I am trying to do the following:
run a command that looks at a binary file and formats it
find the first line that has what I am looking for (there will be multiple)
print the name of the file that has it
So I am running this but ti's not working
ls -ltr *20080612* | while read line... (3 Replies)
Discussion started by: llsmr777
3 Replies
3. Shell Programming and Scripting
Hi
I want to split a file that has 'n' number of records into 16 small files.
Can some one suggest me how to do this using Unix script?
Thanks
rrkk (10 Replies)
Discussion started by: rrkks
10 Replies
4. Solaris
I got the following info from this forum, in regards to configuring my
Solaris x86 to link to the Net:
# echo 192.168.0.1 > /etc/defaultrouter
# route add default 192.168.0.1
# echo nameserver 192.168.0.1 >> /etc/resolv.conf
# cp /etc/nsswitch.dns /etc/nsswitch.conf
So I did... (1 Reply)
Discussion started by: newbie09
1 Replies
5. Red Hat
Hi, I facing an NFS problem. I have machine1, which has diskA and diskB, and machine2, both are Mandriva 2009 Linux.
When I am on machine2 and NFS mount both diskA and diskB of machine1. Writing to diskA is very fast, but writing to diskB is very slow. I tried different mount rsize and wsize... (2 Replies)
Discussion started by: hiepng
2 Replies
6. Red Hat
Hi guys,
I am trying something. I wrote a simple shell program to test something where continuous while loop writes on a file over the nfs. The time taken to write "hello" 3000 times take about 10 sec which is not right. Ideally it should take fraction of seconds. If I write on the local disk, it... (1 Reply)
Discussion started by: abhig
1 Replies
7. Shell Programming and Scripting
Anyone know the best way to check and see if a NAS filesystem is mounted on a linux box. I have no idea where to start :wall:. (2 Replies)
Discussion started by: d3mon_spawn
2 Replies
8. Solaris
there are few nas shares that would be mounted on the local zone. should i add an entry into the add an entry in zone.xml file so that it gets mounted automatically when the zone gets rebooted? or whats the correct way to get it mounted automatically when the zone reboots (2 Replies)
Discussion started by: chidori
2 Replies
9. Solaris
Hi,
I am facing chgrp issue for a directory on a NAS mounted partation.
issue details :
user1 belongs to two groups grp1(primary) and grp2(secondary) not able to change directory group to secondary.
WORKING on /tmp
#mkdir /tmp/a
#ls -ld /tmp/a
drwxr-xr-x 2 user1 grp1 117 Mar 24... (7 Replies)
Discussion started by: naveen.surisett
7 Replies
10. Red Hat
Dear friends,
I have been facing an issue with one of my red hat unix machine, suddenly lost to switch sudo users. My all colleagues lost to switch to access sudo users.
Then, we have realized its related to NAS issue which does not allowing to write the file. because of this we got so many... (1 Reply)
Discussion started by: Chand
1 Replies
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)