I'm having trouble getting the 9.1 NFS server to allow read-write mounts. My /etc/exports (on bigbear) says: / 10.64.0.0/255.248.0.0(rw,norootsquash) / 10.254.0.0/255.248.0.0(rw,norootsquash) /tmp 10.254.0.0/255.248.0.0(rw,norootsquash) /tmp 10.r4.0.0/255.248.0.0(rw,norootsquash) When I mount / or /tmp from a remote system, with or without "-o rw" in the mount command, it says the mount is read-write, but any attempt to write to it fails: fs-sw2:~ # mount /dev/hda6 on / type ext2 (rw) proc on /proc type proc (rw) /dev/hda5 on /boot type ext2 (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=0620) automount(pid130) on /misc type autofs (rw,fd=5,pgrp=130,minproto=2,maxproto=3) bigbear:/tmp on /mnt type nfs (rw,addr=10.64.6.51) fs-sw2:~ # echo testing >/mnt/junk bash: /mnt/junk: Read-only file system The same behavior occurs whether the remote system is SuSE 6.3, 8.0, or 9.1. I can mount RW from the 9.1 system to the others without problem. I can't find anything in Yast2 that gives a clue. Is there something I'm doing wrong? TIA, Jim
On Tuesday 11 Jan 2005 18:06 pm, Jim Cunning wrote:
I'm having trouble getting the 9.1 NFS server to allow read-write mounts. My /etc/exports (on bigbear) says: <SNIP> The same behavior occurs whether the remote system is SuSE 6.3, 8.0, or 9.1. I can mount RW from the 9.1 system to the others without problem. I can't find anything in Yast2 that gives a clue. Is there something I'm doing wrong?
Which versions of nfs are running on each box? Dylan
TIA, Jim
-- "I see your Schwartz is as big as mine" -Dark Helmet
On 10:06 Tue 11 Jan , Jim Cunning wrote:
I'm having trouble getting the 9.1 NFS server to allow read-write mounts. My /etc/exports (on bigbear) says:
/ 10.64.0.0/255.248.0.0(rw,norootsquash) / 10.254.0.0/255.248.0.0(rw,norootsquash) /tmp 10.254.0.0/255.248.0.0(rw,norootsquash) /tmp 10.r4.0.0/255.248.0.0(rw,norootsquash)
When I mount / or /tmp from a remote system, with or without "-o rw" in the mount command, it says the mount is read-write, but any attempt to write to it fails:
fs-sw2:~ # mount /dev/hda6 on / type ext2 (rw) proc on /proc type proc (rw) /dev/hda5 on /boot type ext2 (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=0620) automount(pid130) on /misc type autofs (rw,fd=5,pgrp=130,minproto=2,maxproto=3) bigbear:/tmp on /mnt type nfs (rw,addr=10.64.6.51)
fs-sw2:~ # echo testing >/mnt/junk bash: /mnt/junk: Read-only file system
The same behavior occurs whether the remote system is SuSE 6.3, 8.0, or 9.1. I can mount RW from the 9.1 system to the others without problem. I can't find anything in Yast2 that gives a clue. Is there something I'm doing wrong?
TIA, Jim
Have you tried, 'rw,no_root_squash'? On mine, the format requires the underline separator. HTH...? -- ..."Yogi" CH Namasté Yoga Studio
Today at 1:05pm, C Hamel wrote:
Have you tried, 'rw,no_root_squash'? On mine, the format requires the underline separator.
Bingo!! It helps to read the man page _carefully_, and then read it again, even if you think you know the syntax. Thanks for the clue. Jim
The Tuesday 2005-01-11 at 10:06 -0800, Jim Cunning wrote:
The same behavior occurs whether the remote system is SuSE 6.3, 8.0, or 9.1. I can mount RW from the 9.1 system to the others without problem. I can't find anything in Yast2 that gives a clue. Is there something I'm doing wrong?
Sorry, I don't get a clear picture of what versions you have on the server and the clients. "Remote" could both apply to server or client. -- Cheers, Carlos Robinson
On Jan 12 at 1:04am, Örn Einar Hansen wrote:
Þann Þriðjudagur 11 janúar 2005 19:06 skrifaði Jim Cunning:
fs-sw2:~ # echo testing >/mnt/junk bash: /mnt/junk: Read-only file system
Try doing this same command, as a normal user.
The problem was specifying "norootsquash" instead of "no_root_squash" in /etc/exports, making the mount RO for all users, root included. See my earlier [SOLVED] post. Jim
participants (5)
-
C Hamel
-
Carlos E. R.
-
Dylan
-
Jim Cunning
-
Örn Einar Hansen