LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (http://www.linuxquestions.org/questions/linux-server-73/)
-   -   NFS share mounts with ro rather than rw for a new client (http://www.linuxquestions.org/questions/linux-server-73/nfs-share-mounts-with-ro-rather-than-rw-for-a-new-client-590348/)

dustymugs 10-08-2007 03:55 PM

NFS share mounts with ro rather than rw for a new client
 
Howdy all,

I have a new client box (slackware 12 w/ 2.6.22.9) accessing an existing server (slackware 11 w/ 2.6.20.4) with several nfs exports. The server's nfs configs are:

/etc/exports
Code:

/data/cin              192.168.135.0/255.255.255.0(rw,subtree_check)
/data/cout      192.168.135.0/255.255.255.0(rw,subtree_check)
/data/temp      192.168.135.0/255.255.255.0(rw,subtree_check)

/etc/hosts.allow

Code:

portmap: 192.168.135.0/255.255.255.0
lockd: 192.168.135.0/255.255.255.0
mountd: 192.168.135.0/255.255.255.0
rquotad: 192.168.135.0/255.255.255.0
statd: 192.168.135.0/255.255.255.0

/etc/hosts.deny

Code:

portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL

The server's /proc/fs/nfs/exports:

Code:

# Version 1.1
# Path Client(Flags) # IPs
/data/cin      192.168.135.0/255.255.255.0(rw,root_squash,sync,wdelay)
/data/temp      192.168.135.0/255.255.255.0(rw,root_squash,sync,wdelay)
/data/cout      192.168.135.0/255.255.255.0(rw,root_squash,sync,wdelay)

When I mount any of the read/write exports (cin, temp, cout) on the client, the effect is that the mount is read-only. Various outputs from the client are:

mount

Code:

...
data.hades.local:/data/cin on /data/cin type nfs (rw,hard,intr,addr=192.168.135.1)
data.hades.local:/data/cout on /data/cout type nfs (rw,hard,intr,addr=192.168.135.1)
nfsd on /proc/fs/nfs type nfsd (rw)

cat /proc/mounts

Code:

...
data.hades.local:/data/cin /data/cin nfs ro,vers=3,rsize=32768,wsize=32768,hard,intr,proto=udp,timeo=7,retrans=3,sec=sys,addr=data.hades.local 0 0
data.hades.local:/data/cout /data/cout nfs ro,vers=3,rsize=32768,wsize=32768,hard,intr,proto=udp,timeo=7,retrans=3,sec=sys,addr=data.hades.local 0 0
nfsd /proc/fs/nfs nfsd rw 0 0

What doesn't make sense is why the client's mount output shows the nfs mounts as "rw" and the /proc/mounts shows "ro". Any ideas?

I checked on a separate client (slackware 11 w/ 2.4.26) that has been accessing this same server for about a year now and it has no problems writing.

Any help would be great!

Thanks,
dustymugs

PS: And yes, I am aware of /etc/mtab as far as mount is concerned. Repeated tests of mounting show the same ro/rw issue in mount (/etc/mtab) vs /proc/mounts.

dustymugs 10-08-2007 05:23 PM

NFS version mixing is the problem... I think
 
removed as my own answer didn't work longer than a reboot.


All times are GMT -5. The time now is 04:28 AM.