Re: Sol 8 Sparc / Linux 2.2.17 TCP interoperability problems
On Sat, 23 Sep 2000, Horst von Brand wrote: >Some other funny stuf is happening, I'll try on monday without NFSv3 in >kernel, and mounting from the PC. I will add, Solaris ignores the capabilities of mountd and will attempt an NFSv3 connection if it sees a v3 nfsd registered. You can tell mountd to not register for v3, but knfsd registers everything it knows. BTW, Solaris 8 is likely attempting to use web-nfs -- even if you tell it not to. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Sol 8 Sparc / Linux 2.2.17 TCP interoperability problems
Chris Pascoe <[EMAIL PROTECTED]> said: > Is anyone else experiencing an interoperability problem when running the > nfs-utils 0.1.9.1 or 0.2 on an (unpatched) 2.2.16 or 2.2.17 kernel NFS > Server, exporting to a Solaris 8 Sparc (patched with recommended patches > as of 6/Sep/2000) client. (Am I the only one trying this config?) I had > a brief look through the nfs and linux-kernel mailing archives and didn't > come across anything mentioning this NFS combination (with the new > nfs-utils, at least). I'm having troubles exporting NFS to Solaris 2.6 on SPARC from linux-2.2.18pre9 with nfs-utils from Red Hat 6.2 updates and also with 0.2. The Solaris complains NFS isn't registered; while the same kernel on a i686 with up to date Red Hat 6.2 mounts fine (while "rpcinfo -u server nfs" says it just isn't there ;-) Some other funny stuf is happening, I'll try on monday without NFSv3 in kernel, and mounting from the PC. Be advised thay the NFS code in 2.2.17 and before is gone, 2.2.18pre9 has the latest NFS code (which where Trond's patches up to then). -- Horst von Brand [EMAIL PROTECTED] Casilla 9G, Vin~a del Mar, Chile +56 32 672616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Sol 8 Sparc / Linux 2.2.17 TCP interoperability problems
Is anyone else experiencing an interoperability problem when running the nfs-utils 0.1.9.1 or 0.2 on an (unpatched) 2.2.16 or 2.2.17 kernel NFS Server, exporting to a Solaris 8 Sparc (patched with recommended patches as of 6/Sep/2000) client. (Am I the only one trying this config?) I had a brief look through the nfs and linux-kernel mailing archives and didn't come across anything mentioning this NFS combination (with the new nfs-utils, at least). The problem that I appear to see is that the setsockopt(..., SO_RCVBUF, 1024..) which occurs in support/nfs/rpcmisc.c (during the mountd process) seems to cause a situation where no data can be received from the showmount's TCP connection; the Linux TCP stack refuses to acknowledge any data received from the Sun box. Removing the setsockopt() calls or increasing the rcvbuf size by nine bytes to 1033 resolves the problem. A brief tcpdump showing the behaviour for the two cases, and some standalone test code which demonstrates the problem on my systems (without needing to break / setup mountd) is available at: http://celab21.pc.elec.uq.edu.au/~chris/tcpbug/ I lack the level of understanding of the Linux 2.2.x TCP stack needed to resolve the problem alone, but it seems the behaviour I am seeing may be related to some things discussed /changes made during the 'select()/socket has problems under 2.2.x' thread on linux-kernel around March last year. Chris Pascoe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Sol 8 Sparc / Linux 2.2.17 TCP interoperability problems
Is anyone else experiencing an interoperability problem when running the nfs-utils 0.1.9.1 or 0.2 on an (unpatched) 2.2.16 or 2.2.17 kernel NFS Server, exporting to a Solaris 8 Sparc (patched with recommended patches as of 6/Sep/2000) client. (Am I the only one trying this config?) I had a brief look through the nfs and linux-kernel mailing archives and didn't come across anything mentioning this NFS combination (with the new nfs-utils, at least). The problem that I appear to see is that the setsockopt(..., SO_RCVBUF, 1024..) which occurs in support/nfs/rpcmisc.c (during the mountd process) seems to cause a situation where no data can be received from the showmount's TCP connection; the Linux TCP stack refuses to acknowledge any data received from the Sun box. Removing the setsockopt() calls or increasing the rcvbuf size by nine bytes to 1033 resolves the problem. A brief tcpdump showing the behaviour for the two cases, and some standalone test code which demonstrates the problem on my systems (without needing to break / setup mountd) is available at: http://celab21.pc.elec.uq.edu.au/~chris/tcpbug/ I lack the level of understanding of the Linux 2.2.x TCP stack needed to resolve the problem alone, but it seems the behaviour I am seeing may be related to some things discussed /changes made during the 'select()/socket has problems under 2.2.x' thread on linux-kernel around March last year. Chris Pascoe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Sol 8 Sparc / Linux 2.2.17 TCP interoperability problems
On Sat, 23 Sep 2000, Horst von Brand wrote: Some other funny stuf is happening, I'll try on monday without NFSv3 in kernel, and mounting from the PC. I will add, Solaris ignores the capabilities of mountd and will attempt an NFSv3 connection if it sees a v3 nfsd registered. You can tell mountd to not register for v3, but knfsd registers everything it knows. BTW, Solaris 8 is likely attempting to use web-nfs -- even if you tell it not to. --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
