NFS problem on Solaris 8


 
Thread Tools Search this Thread
Operating Systems Solaris NFS problem on Solaris 8
# 1  
Old 05-31-2008
NFS problem on Solaris 8

I have problem to map directory from the client. But here is what I have done on the server

# exportfs
- /export/home/sefas/director/traffic rw ""

# ps -ef|grep nfs
root 192 1 0 May 20 ? 0:00 /usr/lib/nfs/lockd
daemon 193 1 0 May 20 ? 0:00 /usr/lib/nfs/statd
root 865 1 0 20:35:05 ? 0:00 /opt/SUNWpcnfs/sbin/rpc.pcnfsd
root 876 1 0 20:35:26 ? 0:00 /opt/SUNWpcnfs/sbin/rpc.pcnfsd
root 1633 767 0 21:28:50 pts/4 0:00 grep nfs


But after I try to map the export drive, the error shows "server not accesible"

Please help me ou
Thank you
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

NFS write error on host xyz: Stale NFS file handle - Solaris 10

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

NFS mount on Solaris 8

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

NFS on a Solaris 9 server

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

Window NFS VS Solaris NFS

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

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

6. Solaris

My solaris nfs is odd.

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

problem NFS mounting onto Solaris 10

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

solaris 8 NFS mounting problem

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

Problem with NFS server (Solaris 10)

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

nfs on solaris

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
Login or Register to Ask a Question
exportfs(8)						      System Manager's Manual						       exportfs(8)

NAME
exportfs - maintain list of NFS exported file systems SYNOPSIS
/usr/sbin/exportfs [-avi] [-o options,..] [client:/path ..] /usr/sbin/exportfs -r [-v] /usr/sbin/exportfs [-av] -u [client:/path ..] /usr/sbin/exportfs [-v] /usr/sbin/exportfs -f DESCRIPTION
The exportfs command is used to maintain the current table of exported file systems for NFS. This list is kept in a separate file named /var/lib/nfs/etab which is read by mountd when a remote host requests access to mount a file tree, and parts of the list which are active are kept in the kernel's export table. Normally this etab file is initialized with the list of all file systems named in /etc/exports by invoking exportfs -a. However, administrators can choose to add and delete individual file systems without modifying /etc/exports using exportfs. exportfs and it's partner program mountd work in one of two modes, a legacy mode which applies to 2.4 and earlier versions of the Linux kernel, and a new mode which applies to 2.6 and later versions providing the nfsd virtual filesystem has been mounted at /proc/fs/nfsd or /proc/fs/nfs. If this filesystem is not mounted in 2.6, the legacy mode is used. In the new mode, exportfs does not give any information to the kernel but only provides it to mountd through the /var/lib/nfs/etab file. mountd will listen to requests from the kernel and will provide information as needed. In the legacy mode, any export requests which identify a specific host (rather than a subnet or netgroup etc) are entered directly into the kernel's export table as well as being written to /var/lib/nfs/etab. Further, any mount points listed in /var/lib/nfs/rmtab which match a non host-specific export request will cause an appropriate export entry for the host given in rmtab to be entered into the kernel's export table. OPTIONS
-a Export or unexport all directories. -o options,... Specify a list of export options in the same manner as in exports(5). -i Ignore the /etc/exports file, so that only default options and options given on the command line are used. -r Reexport all directories. It synchronizes /var/lib/nfs/etab with /etc/exports. It removes entries in /var/lib/nfs/etab which are deleted from /etc/exports, and remove any entries from the kernel export table which are no longer valid. -u Unexport one or more directories. -f In 'new' mode, flush everything out of the kernels export table. Any clients that are active will get new entries added by mountd when they make their next request. -v Be verbose. When exporting or unexporting, show what's going on. When displaying the current export list, also display the list of export options. DISCUSSION
Exporting Directories The first synopsis shows how to invoke the command when adding new entries to the export table. When using exportfs -a, all directories in exports(5) are added to etab and the resulting list is pushed into the kernel. The host:/path argument specifies the directory to export along with the host or hosts to export it to. All formats described in exports(5) are supported; to export a directory to the world, simply specify :/path. The export options for a particular host/directory pair derive from several sources. There is a set of default options which can be over- ridden by entries in /etc/exports (unless the -i option is given). In addition, the administrator may override any options from these sources using the -o argument which takes a comma-separated list of options in the same fashion as one would specify them in exports(5). Thus, exportfs can also be used to modify the export options of an already exported directory. Modifications of the kernel export table used by nfsd(8) take place immediately after parsing the command line and updating the etab file. The default export options are sync,ro,root_squash,wdelay. Unexporting Directories The third synopsis shows how to unexported a currently exported directory. When using exportfs -ua, all entries listed in etab are removed from the kernel export tables, and the file is cleared. This effectively shuts down all NFS activity. To remove an export to a host, specify a host:/path pair. This deletes the specified entry from etab and removes the corresponding kernel entry (if any). To remove one or more exports to several hosts, use exportfs -ua. Dumping the Export Table Invoking exportfs without further options shows the current list of exported file systems. When giving the -v option, the list of flags pertaining to each export are shown in addition. EXAMPLES
The following adds all directories listed in /etc/exports to /var/lib/nfs/etab and pushes the resulting export entries into the kernel: # exportfs -a To export the /usr/tmp directory to host django, allowing asynchronous writes, one would do this: # exportfs -o async django:/usr/tmp To unexport the /usr/tmp directory: # exportfs -u django:/usr/tmp To unexport all the directories listed in /etc/exports: # exportfs -au DEPENDENCIES
Exporting to IP networks, DNS and NIS domains does not enable clients from these groups to access NFS immediately; rather, these sorts of exports are hints to mountd(8) to grant any mount requests from these clients. This is usually not a big problem, because any existing mounts are preserved in rmtab across reboots. When unexporting a network or domain entry, any current exports to members of this group will be checked against the remaining valid exports and if they themselves are no longer valid they will be removed. SEE ALSO
exports(5), mountd(8) AUTHORS
Olaf Kirch, <okir@monad.swb.de> Neil Brown, <neilb@cse.unsw.edu.au> 18 July 2003 exportfs(8)