08-28-2014
Please use code tags as required by forum rules!
What IP is your client? That nfs- export is visible to subnet 10.0.0 only, with a 24 bit subnetmask, so a router will be needed between server and allowed clients. Unfortunately, I don't have any experience with nfs across routers.
10 More Discussions You Might Find Interesting
1. OS X (Apple)
Hi all !
I am looking for a command in the terminal or GUI to mount
an NFS drive.
Second , is there any solution to get rid of / " * in old files names
I know it can be done i just dont know how !
Hope that some one can help
Best R.
Yovel (2 Replies)
Discussion started by: yoveln
2 Replies
2. Linux
Hi,
Re-building linux server from a kickstart image on cdrom.
We have a kickstart server.
the cdrom contacins the kickstart ks.cfg file and does a NFS mount from an IP to load the iso images and other files needed during the kickstart (re-build)
Now for some reason the kickstart stops and... (2 Replies)
Discussion started by: Andrek
2 Replies
3. Solaris
On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line:
share -F nfs -o rw /export/home/data
In the /etc/hosts.equiv file, I have this:
+
When I do a "ps -ef" command, I see that the "nfsd' daemon is started.
... (2 Replies)
Discussion started by: serendipity1276
2 Replies
4. UNIX for Advanced & Expert Users
Hi Guru's,
I am unable to mount NFS share on unix system (DG/UX) which is nfs client.
Error:
mount: /nfsshare: Invalid argument
mount: giving up on:
/mountpoint
i tried following command
mount -t nfs remotehost:/nfsshare /mountpoint
Error: (5 Replies)
Discussion started by: Justin John
5 Replies
5. Solaris
Hello, I am looking for some assistance in mounting an nfs drive on boot, on a Solaris 11 machine.
On my Solaris 9/10 machines, I have an entry for my nfs mount in /etc/vfstab, however when I add the same entry to my vfstab on Solaris 11, the drive will not mount on boot. After booting up, I... (5 Replies)
Discussion started by: bstring
5 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I need to mount an nfs filesystem as below.
xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs
For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work?
mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
7. Red Hat
Hello,
We have NFS server setup on CentOS5.6 x64bit with nfs 3 version.
Now we have setup a another server CentOS6.4 x64 bit and going to mount nfs location (Which setup on CentOS5.6 x64bit). Now when i am mounting this location on CentOS6.4 x63 bit, below error is displaying.
# mount -o... (2 Replies)
Discussion started by: sunnysthakur
2 Replies
8. UNIX for Advanced & Expert Users
Hi,
I would like to know how can we mount a directory using nfs v4 ?
When I use the below command, I am not sure what nfs version am using to mount the directory.
mount -t <server_name>:<shared_directory> <shared_directory>.
eg:
mount -t 10.50.0.8:/home/arun/mount/share_dir... (7 Replies)
Discussion started by: arunsriniv
7 Replies
9. Red Hat
The server ip is 10.2.2.24. I have installed nfs-utils package the i have edited /etc/exports
i have added the following line
/home 10.2.2.0/24(rw,sync,no_root_squash,no_all_squash)
i have saved, i have started the nfs service, then i am trying to mount nfs sharing from client machine using... (1 Reply)
Discussion started by: ainstin
1 Replies
10. Solaris
Hi,
I am having some issues mounting NFS files.
for some reason the mount -F nfs is not being recognized..
bash-3.2# mount -F nfs -o rw 192.168.245.129:/mnt/nfs1/ /mnt
UX:vxfs mount: ERROR: V-3-20135: FSType nfs not recognized
UX:vxfs mount: INFO: V-3-20147: Usage:
mount {special |... (5 Replies)
Discussion started by: br1an
5 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)