Apologies for the long turn-around on this, but I've been off in
bug-squashing mode...
No, I haven't tried the included nfs root support (you mean the
install-over-nfs feature?). But as you say, it shouldn't have much
bearing on an NFS mount being read-write or read-only in my case.
The only messages on the server, in /var/log/messages, are of the form:
rpc.mountd: authenticated mount request from mynode:881 for
/remote/dir/foo (/remote/dir)
I don't see any errors or warnings indicating a problem, and there's no
warning on the client side that the mount is being done read-only. It
just is, and I get EROFS if I try to create, modify or delete a file on
the mounted filesystem.
Chris
Bill Nottingham wrote:
Chris Johns ([EMAIL PROTECTED]) said:
No, it's a custom initrd image (gzipped ext2 filesystem image), but a
stock non-xen kernel.
It's tangential to this, but have you tried the included nfs root
support?
mount /proc and /sys
mount the root filesystem read-only over NFS
unmount /proc and /sys
pivot_root to the NFS root
mount /proc and /sys again
mount more filesystems read-write
The NFS server is an ELAS3u6 system, and it's exporting the directories
read-write. I can drop to a shell (bash) from the linuxrc script and
issue the mount by hand, and I get the same results: it succeeds, but is
read-only.
Any messages on the server?
Bill
_______________________________________________
rhelv5-beta-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
_______________________________________________
rhelv5-beta-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-beta-list
