Sponsored Content
Full Discussion: Solaris 10 NFS Share Issue
Operating Systems Solaris Solaris 10 NFS Share Issue Post 302760869 by hicksd8 on Thursday 24th of January 2013 05:01:38 PM
Old 01-24-2013
I agree that this is weird, especially since I do this all the time between Solaris 10 boxes with no issues. I appreciate that doesn't help you.

Having looked at how I configure mine, I notice one major difference:

Quote:
Here is what I have in /etc/vfstab on the client:

server:/share - /share nfs - yes rw

In vfstab on clients I always use:

Code:
 
server:/share - /share nfs - yes rw,soft

for soft not hard (default) mount

Other than that I can't spot any differences.

Perhaps cut and post the actual vfstab and dfstab contents in case I can see a syntax error or the like.

I confgure dfstab on the server side as you are doing it.

I admit that I am confused.

Last edited by hicksd8; 01-24-2013 at 06:14 PM..
 

10 More Discussions You Might Find Interesting

1. Solaris

how to mount Windows NFS share on solaris

Hi, How can i mount an NFS share on a solaris machine a filesystem ? I have enabled nfs on a windows server and the shares has given read/write access to it to all the users. I would like to mount it on around 10 different solaris boxes with different versions of solaris. Thanks in advance. (2 Replies)
Discussion started by: uxadmin007
2 Replies

2. Windows & DOS: Issues & Discussions

VxWorks - W2003 issue loading file from NFS share

We recently replaced an existing Windows Server 2000 with a Windows Server 2003. The server‘s primary function is file/print in our development environment. One of the directories is shared using NFS. All compiled software is kept in this share (we use C & C++). The generated “.out” and “.ndb”... (0 Replies)
Discussion started by: BigBuff52
0 Replies

3. Solaris

Can't access NFS Share on Solaris Server from a Linux Client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. & then ran the following On the client machine, while running the mount command, I am... (0 Replies)
Discussion started by: SunilB2011
0 Replies

4. Red Hat

Unable to access NFS share on Solaris Server from Linux client

Hi, I am trying to access a NFS shared directory on Solaris 10 Server from a client which is RHEL 4 Server. On the NFS Server, in /etc/dfs/, I added following line to dfstab file. share -F nfs -o rw /var/share & then ran the following svcadm -v enable -r... (3 Replies)
Discussion started by: SunilB2011
3 Replies

5. UNIX for Advanced & Expert Users

NFS : Invalid argument (Remote share mounting issue)

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

6. Solaris

Mounting 2012R2 NFS Share on Solaris 10

Hi all, new here. I'm attempting to mount an NFS share I've created on a 2012r2 esx VM on my solaris 10 vm, I'm using the following command: mount 2012box:/sharename /mnt and I get the following result: nfs mount: mount: /mnt: Operation not supported Both vms can ping one... (3 Replies)
Discussion started by: Meshuggener
3 Replies

7. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

8. Solaris

RHEL NFS share on Solaris 11.3 vers=4

NFS server: RHEL:6 /nfsdb 192.168.8.10/28(rw,sync,no_root_squash) 192.168.7.10/28(rw,sync,no_root_squash) Client: Solaris 11.3 vfstab entry : 192.168.8.9:/nfsdbarch - /archive_data nfs - yes rw,soft,vers=4 # ls -ld /archive_data drwxr-xr-x 4 root root... (3 Replies)
Discussion started by: Shirishlnx
3 Replies

9. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies

10. Solaris

Default route issue in share local zone in Solaris 11

Hi We took the reboot of server/global zone after that Solaris 11 share local zone not able to ping the default gateway but global zone able to ping same default gateway. I check/compare the before activity logs of global zone and local zones which looks fine to me, further IP and netmask of... (6 Replies)
Discussion started by: sb200
6 Replies
share(1M)																 share(1M)

NAME
share - make local resource available for mounting by remote systems SYNOPSIS
FSType] specific_options] description] [pathname] DESCRIPTION
The command exports, or makes a resource available for mounting, through a remote file system of type FSType. If the option is omitted, the first file system type listed in is used as default. For a description of NFS specific options, see share_nfs(1M). pathname is the pathname of the directory to be shared. When invoked with no arguments, displays all shared file systems. Options recognizes the following options: Specify the file system type. The specific_options are used to control access of the shared resource. (See share_nfs(1M) for NFS specific options.) They may be any of the following: pathname is shared read/write to all clients. This is also the default behavior. Share the pathname read-mostly if option is not provided. Read-mostly means read-write to those clients specified and read-only for all other systems. If a option is provided, pathname is shared read/write only to the listed clients. No other systems can access pathname. pathname is shared read-only to all clients. pathname is shared read-only only to the listed clients. No other systems can access pathname. The flag may be used to provide a description of the resource being shared. WARNINGS
Old terminology (export) File system sharing used to be called on HP-UX, and was used for exporting file systems. With the new share NFS model, the command replaces exportfs(1M) or To support compatiblity with scripts that still invoke the exportfs command using the access= option, the share command will not fail when the access option is used and the syntax matches the usage of exportfs(1M) from a release of HP-UX that does not support the share(1M) com- mand. Attempts to use the access option with new share options, (i.e. sec=), may result in the access option begin rejected by the share command. It is highly recommended that the access option not be used with the share command. Instead, use the ro= and rw= option to achieve the desired access restrictions. This support of the access= option will be removed in a future release of HP-UX. If commands are invoked multiple times on the same file system, the last invocation supersedes the previous; the options set by the last command replace the old options. For example, if read-only permission was previously given to on use the following command to also give read-only permission to on This behavior is not limited to sharing the root file system, but applies to all file systems. EXAMPLES
The following command wll share the file system read-only. FILES
list of commands to be executed at boot time list of distributed file system types, NFS by default system record of shared file systems AUTHOR
was developed by Sun Microsystems, Inc. SEE ALSO
mountd(1M), nfsd(1M), share_nfs(1M), shareall(1M), unshare(1M), dfstab(4), fstypes(4), sharetab(4). share(1M)
All times are GMT -4. The time now is 07:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy