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!
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.
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.
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.
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).
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)
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)
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)
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)
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)
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)
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)
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)
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)