http://bugzilla.novell.com/show_bug.cgi?id=495130 User sjayaraman@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=495130#c1 Suresh Jayaraman <sjayaraman@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |hpj@urpla.net --- Comment #1 from Suresh Jayaraman <sjayaraman@novell.com> 2009-05-12 07:38:50 MDT --- Thanks for the bug report. Looking at the traces, there were no portmap GETPORT calls. There was only a DUMP call but the client was not trying to use the mountd port returned as part of DUMP reply from the server. The client sends mount request but to the wrong port - 627 is the not server's mountd port. Does using "mountport=<port>" option help? (mount port can be obtained from rpcinfo -p (mountd vers 3) AFAICT, Rpcbind is backward compatible but not sure whether a it works fine with a kernel that is as old as 2.6.11 (present in 9.3). It is not clear why client is not sending GETPORT calls but still using a port where mountd is not listening. Similarly it is not clear why the problem goes away while replacing rpcbind with portmap. Enabling rpc debugging might give some clues. Can you enable rpc debugging on both client and server by doing: echo 65535 > /proc/sys/sunrpc/rpc_debug and attach the dmesg/syslog output? Also, if possible see whether the problem is reproducible with client > 9.3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.