I start to use NFS over my LAN and it rolls.
However, there's a write problem from 2.2.5 kernel
machine ("roll") onto 2.0.36 kernel machine
("yaw"), and also a mount problem for yaw mounting
roll. Even when I specify
/usr/local roll(rw)
in yaw's /etc/exports, roll still can't write onto
yaw! "In a simultaneous but probably unrelated
incident," yaw can't mount roll at all: when I
mumble
[khrabrov@yaw get]$ mount -o rsize=1024,wsize=1024 roll:/usr/local /mnt/roll
the darnedest thing replies that /mnt/roll is busy
or already mounted, which is a blatant lie. Both
exports specify (rw) after the other machine's name.
Is there any other piece of NFS configuration
which comes into play here? NFS-HOWTO mentions
that 2.2 kernel NFS has significant changes. I
see that some lock managers are reported by
rpcinfo -i on 2.2.5 which are not present on
2.0.36. What are they and are they related?
--
Cheers,
Alexy Khrabrov -- www.suffix.com -- Segmentation f%^(&
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
