| Summary: | NFS mageia-mandriva slow depending on who establishes connection | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Arthur Dent <slartibart70> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | guillomovitch, stormi-mageia |
| Version: | 1 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Arthur Dent
2011-06-29 09:58:09 CEST
Guillomovitch, is there something you could do to help debugging this? (if not, and if you have another name to give to me, I take it :)) CC:
(none) =>
guillomovitch, stormi From the mount string, you're probably using NFSv4 in the one case (mageia -> mandriva), and NFSv3 in the other case (mandriva -> mageia). That's probably due to protocol negociation failure in the second case, due to a missing NFSv4-specific component (rpc.idmapd, probably). Also, you need to use rpcbind, not portmap, for NFSv4. And if running on a private local network segment, using tcpwrapper is probably overkill (but that's up to you). On both sides, check your /etc/sysconfig/nfs-common file for NEED_IDMAPD parameter, and use 'service nfs-common status' to check if rpc.idmapd is running. If not enough, you can force protocol version with nfsvers parameter, and also use mount -v flag for details. Also, don't bother with rsize and wsize parameters, they're quite useless excepted in a few scenarios. Status:
NEW =>
ASSIGNED This problem is now 6 month old, and is likely to be a local configuration issue. I'm closing it, given the lack of interest from original reporter. Status:
ASSIGNED =>
RESOLVED |