Solaris 10 NFS Share Issue


Login or Register to Reply

 
Thread Tools Search this Thread
# 1  
Old 01-22-2013
Solaris 10 NFS Share Issue

Hello all,

I am having an issue with an NFS share I have created between two Solaris 10 boxes. I want the share to have read/write permissions, but for some reason it is coming up as read-only on the client side mount despite "rw" being specified in the mount options.

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

server:/share - /share nfs - yes rw

Here is what I have in /etc/dfs/dfstab on the server:

share -F nfs -o rw,root=clientservername /share

The problem appears to be with the client-side mount, because if I perform the following command it becomes read-write:

mount -o remount /share

Any ideas why the share started out as read-only despite being specified otherwise? Any help is greatly appreciated!

Regards,

Chris
# 2  
Old 01-22-2013
Please post the /share directory permissions on the server.

Who is the owner?

(Could try setting to 777 and see if the problem goes away)
# 3  
Old 01-22-2013
The owner is root and the permissions are currently 755, but I currently have read/write after performing the remount option. I am troubleshooting this on a production server, so I have not had a chance to reboot the server to see if it reverts to read-only (I suspect it will since it started out that way), but when I do I will give 777 a shot.

Thanks,

Chris
# 4  
Old 01-24-2013
Unfortunately I tried setting the permissions to 777, but it still comes up as read-only initially. So everytime the system reboots or the NFS client service is restarted...it comes up as read-only and I have to use the remount command to fix it. I also tried forcing NFSv4 just to see if that changes anything, but no change.

I just find it odd that the remount command is supposed to mount an already mounted share adding in the "rw" option even though I already mounted it with the rw option in the first place.

Regards,

Chris
# 5  
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..
# 6  
Old 01-25-2013
Weird. Try mounting with "-o vers=3,proto=tcp" and see what happens.

And don't use soft mounts. Soft mounts do not support mmap'd files because once a file is mmap'd, the system assumes any pages needed can be read/written as necessary and there is no way to tell a running application otherwise. This can lead to processes crashing with SEGV/SIGBUS and/or data corruption. Also, writes cached on the client can be lost if the IO attempt times out after the application received a successful return from its write() call, which can also lead to data corruption. Never mind the fact that you're assuming all applications will properly handle possible intermittent IO errors any reads/writes. If they don't - data corruption.

IMO, if you know you're never going to have mmap'd files (and executables - applications and shared objects - are all mmap'd when they are run...) and ALL the apps running on your system are known to properly handle intermittent IO errors soft mounts are OK.
This User Gave Thanks to achenle For This Post:
radoulov (01-25-2013)
# 7  
Old 01-25-2013
Another thought on this issue..........

On your server can you

Code:
ping <clientname>

just to check that the client name can be resolved. Does it translate to the correct ip address of the client?

If ping cannot resolve the name then neither will the share command and the server will not recognise the inbound nfs mount request as a node it should give rw,root access to. A read-only access might result (I guess).
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Default route issue in share local zone in Solaris 11 sb200 Solaris 6 10-03-2018 02:18 PM
Solaris 10 NFS client cannot mount a share from a Windows server Hiroshi Solaris 1 02-08-2017 07:07 PM
RHEL NFS share on Solaris 11.3 vers=4 Shirishlnx Solaris 3 09-22-2016 08:28 AM
Mount NFS Share On NFS Client via bash script. Brian.t Shell Programming and Scripting 4 03-13-2016 11:03 AM
Mounting 2012R2 NFS Share on Solaris 10 Meshuggener Solaris 3 05-14-2015 06:49 PM
NFS share and groups cjhilinski Red Hat 14 03-11-2015 11:24 AM
Permissions for NFS share Rossdba UNIX for Dummies Questions & Answers 0 08-27-2014 07:58 PM
NFS share mastansaheb Red Hat 1 04-10-2013 04:28 AM
NFS : Invalid argument (Remote share mounting issue) Justin John UNIX for Advanced & Expert Users 5 08-06-2012 04:26 PM
Unable to access NFS share on Solaris Server from Linux client SunilB2011 Red Hat 3 06-22-2012 03:01 AM
Can't access NFS Share on Solaris Server from a Linux Client SunilB2011 Solaris 0 06-21-2012 03:39 AM
VxWorks - W2003 issue loading file from NFS share BigBuff52 Windows & DOS: Issues & Discussions 0 12-12-2011 05:07 PM
how to mount Windows NFS share on solaris uxadmin007 Solaris 2 08-03-2009 04:40 PM
NFS share error rcmrulzz Red Hat 2 05-14-2008 09:05 AM
NFS share options psimoes79 Solaris 6 10-01-2007 03:27 PM