I will call the two Red Hat 6.0 machines server and client.
They share password information via NIS. User john's home
directory is in server:/home/john and server:/home is
exported read-write to the subnet which includes client.
When he logs into client, the home directory is automounted
as client:/homes/john. All files are accessible, but
whenever john tries to write to the filesystem (creating new
files, deleting, etc), access is denied. So when he tries
to execute 'touch testfile' in his home directory, the error
message appears on the terminal:
'touch: testfile: Read-only file system' and the file is not
At the same time, kernel on server logs this message to
kernel: fh_verify: john/.bash_history permission failure,
The syslog on client registers:
nfs_rpc_verify: RPC call rejected: 1
nfs_statfs: statfs error = 5
Needless to say, this mounting worked perfectly when both
machines were RedHat 5.2. The same happens if the server is
Red Hat 6.0 and the client Red Hat 5.2.
IIRC, the convention for access to a file system has changed. In 5.2,
if no access was specified, rw was assumed. In 6.0, ro is assumed.
Try exporting the file system with explicit rw access.
Your recommendation has done the trick. I thought I had tried that
when I was submitting the bug report. I changed the old export entry
192.0.0.0/255.255.255.0 to 192.0.0.0/255.255.255.0(rw) and everything
This problem appears to be fixed.
The documentation is wrong, though. From the exports(5) man page:
ro Allow only read-only requests on this NFS volume.
The default is to allow write requests as well,
which can also be made explicit by using the rw