10 More Discussions You Might Find Interesting
1. 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
2. Solaris
Hello Admins;
I am working around on an issue of NFS mount on Solaris 8 server.
I am trying to mount a remote directory (which is on vlan 146 -solaris 10 server ) on solaris 8 client which is on vlan 10. The firewall rules have been opened, ports are opened.
But when I do
code: mount -F... (7 Replies)
Discussion started by: snchaudhari2
7 Replies
3. UNIX for Advanced & Expert Users
Hello everyone!! Long time, no see!!
I have an issue with a Solaris server that I am working with. I am trying to set up a backup solution for someone that will involve a Solaris 9 server with NFS enabled allowing a Windows machine to map a drive to it (NFS Maestro).
NFS Maestro appears... (3 Replies)
Discussion started by: Jody
3 Replies
4. Solaris
Hi all,
currently i wish to build a NFS server (windows based), is it the I/O speed will slower than the NFS server in Solaris?
any impact, i using the NFS in windows? (2 Replies)
Discussion started by: SmartAntz
2 Replies
5. Solaris
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
6. Solaris
Dear all,
I have an odd question.
We have a lot of solaris computers.
computer A, share some nfs directory(Directory 1, 2. Directory 1 mount disk 1, Directory 2 mount disk2 ).
Computer B, C, D and E, all can showmount -e A, the result is good. they all can see the directory 1 and 2. ... (4 Replies)
Discussion started by: nybruce
4 Replies
7. 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
8. Solaris
While mounting nfs file system I get the following error .
# mount -F nfs jewelex:/back2 /oback2
nfs mount: jewelex:/back2: Permission denied
Following is the permission for oback2
drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2
Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies
9. Solaris
Hello Guys,
I have just joined this forum & hope that I will find a solution to my question.
I have configured NFS shares on my machine solaris 10 (5.10). Shares have rw access for everyone.
Tried starting NFS server daemon with following command.
svcadm -v enable -t network/nfs/server... (3 Replies)
Discussion started by: say_hi_ravi
3 Replies
10. Filesystems, Disks and Memory
Hello,
I've been trying unsuccesfully to mount from a FreeBSD box to a nfs share on a Solaris 8 box. I've run the share command several different ways and unable to get Read-Write access. I can mount but not create any files. Any solutions would be great!
thanks,
Chameleon (3 Replies)
Discussion started by: chameleon854
3 Replies
rpc.mountd(8) System Manager's Manual rpc.mountd(8)
NAME
rpc.mountd - NFS mount daemon
SYNOPSIS
/usr/sbin/rpc.mountd [options]
DESCRIPTION
The rpc.mountd program implements the NFS mount protocol. When receiving a MOUNT request from an NFS client, it checks the request against
the list of currently exported file systems. If the client is permitted to mount the file system, rpc.mountd obtains a file handle for
requested directory and returns it to the client.
Exporting NFS File Systems
Making file systems available to NFS clients is called exporting.
Usually, a file system and the hosts it should be made available to are listed in the /etc/exports file, and invoking exportfs -a whenever
the system is booted. The exportfs(8) command makes export information available to both the kernel NFS server module and the rpc.mountd
daemon.
Alternatively, you can export individual directories temporarily using exportfs's host:/directory syntax.
The rmtab File
For every mount request received from an NFS client, rpc.mountd adds an entry to the /var/lib/nfs/rmtab file. When receiving an unmount
request, that entry is removed. user level part of the NFS service.
However, this file is mostly ornamental. One, the client can continue to use the file handle even after calling rpc.mountd 's UMOUNT proce-
dure. And two, if a client reboots without notifying rpc.mountd , a stale entry will remain in rmtab.
OPTIONS
-d kind or --debug kind
Turn on debugging for kind.
-F or --foreground
Run in foreground (do not daemonize)
-f or --exports-file
This option specifies the exports file, listing the clients that this server is prepared to serve and parameters to apply to each
such mount (see exports(5)). By default, export information is read from /etc/exports.
-h or --help
Display usage message.
-o num or --descriptors num
Set the limit of the number of open file descriptors to num. The default is 256.
-N or --no-nfs-version
This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup-
port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd must be
invoked with the option --no-nfs-version 3 .
-n or --no-tcp
Don't advertise TCP for mount.
-P Ignored (compatibility with unfsd??).
-p or --port num
Force rpc.mountd to bind to the specified port num, instead of using the random port number assigned by the portmapper.
-V or --nfs-version
This option can be used to request that rpc.mountd offer certain versions of NFS. The current version of rpc.mountd can support both
NFS version 2 and the newer version 3.
-v or --version
Print the version of rpc.mountd and exit.
TCP_WRAPPERS SUPPORT
This rpc.mountd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.mountd if they should be
allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow:
mountd: .bar.com
You have to use the daemon name mountd for the daemon name (even if the binary has a different name).
For further information please have a look at the tcpd(8) and hosts_access(5) manual pages.
SEE ALSO
rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8).
FILES
/etc/exports, /var/lib/nfs/xtab.
AUTHOR
Olaf Kirch, H. J. Lu, G. Allan Morris III, and a host of others.
25 Aug 2000 rpc.mountd(8)