From owner-freebsd-stable Tue May 14 2:13:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from marvin.trident-uk.co.uk (mail.trident-uk.co.uk [195.166.16.10]) by hub.freebsd.org (Postfix) with ESMTP id CD3CA37B405; Tue, 14 May 2002 02:13:15 -0700 (PDT) Received: (from root@localhost) by marvin.trident-uk.co.uk (8.11.1/8.11.1) id g4E8uj646814; Tue, 14 May 2002 09:56:45 +0100 (BST) Received: from trident-uk.co.uk (root@mufuf.trident-uk.co.uk [194.207.93.63]) by marvin.trident-uk.co.uk (8.11.1/8.11.1av) with ESMTP id g4E8uiN46800; Tue, 14 May 2002 09:56:44 +0100 (BST) Received: (from jamie@localhost) by trident-uk.co.uk (8.11.6/8.11.6) id g4E9ML755262; Tue, 14 May 2002 10:22:21 +0100 (BST) (envelope-from jamie) Date: Tue, 14 May 2002 10:22:21 +0100 From: Jamie Heckford To: Matthew Dillon Cc: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: NFS Problems with Quantum Snapserver 4100 (BGE Cards!) Message-ID: <20020514102221.A55183@mufuf.trident-uk.co.uk> Reply-To: jamie@tridentmicrosystems.co.uk References: <20020513181756.A53366@mufuf.trident-uk.co.uk> <200205131808.g4DI8JnE069036@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200205131808.g4DI8JnE069036@apollo.backplane.com>; from dillon@apollo.backplane.com on Mon, May 13, 2002 at 11:08:19AM -0700 X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Im pretty sure this has to be related to the Broadcom Cards. I tested it again this morning from the Compaq rack with the bge card in, same problem. tried doing cp -r /usr/ports /data1-home/ (nfs), copied about 1.3M and then froze. Even cd'ing to the directory to try and do an ls caused my shell to freeze, with Ctrl+C failing to provoke a response. Just to confirm it wasn't a snap server issue, I mounted the nfs share on 3 other FreeBSD boxes (4.2-R, 4.3-R and 4.6-PRERELEASE) that have a variety of 3Com and Intel cards installed, tested copying a 2GB mailbox (!), worked fine. /usr/ports... worked fine. Another odd thing i've seen on the box with the broadcom cards is that when connected via ssh, a simple ls on a large directory (held on a local disk) will get about halfway, pause for about a second, then continue. At first I put this down to traffic on my segment but its happening practically all the time, and this is on 100Mbit connection on the same switch. Just a reminder of the troublesome card... bge0: mem 0xf7fb0000-0xf7fbffff irq 5 at device 5.0 on pci1 FYI there on Cisco Catalyst 2924 switches, and yes they are properly configured ;) CC'ed to hackers as its related to a prev. discussion. Thanks for all your help so far Jamie How I wish I went for the other supplier now :) Thus spake Matthew Dillon (dillon@apollo.backplane.com) : > This sounds like a classic MTU problem. Small packets are fine but > when you copy a large file full-sized packets have to start winging > across the network and something doesn't like them. > > The broadcom NICs can handle large MTUs, but the NFS server and/or > network infrastructure may not be able to. Many GigE switches cannot > handle large packets, for example. Try setting the MTU on the broadcom > interface to 1500 if it isn't there already (you may have to > 'route delete' any cached route to the NFS server after making the > change). > > Another possibility is that the broadcom NIC is broken in regards > to handling large packets. Certain bit patterns can cause the hardware > checksum code to fail. If hardware checksums are turned on, turn them > off and see if that helps. > > -Matt > > :Hi, > : > :Im having odd problems with a nfs mount I have which is on a Quantum Snapserver > :Model 4100. > : > :Basically, I have the nfs mount on /data1-home. Small files are fine, but > :whenever I try and copy anything fairly "big" (5MB!) the command prompt > :just sits there. > : > :cd'ing to /data1-home just results in the command hanging there, and the only > :way to get back to the NFS share is the force an umount and remount. > : > :Has anyone had any similar problems? > : > :Im running FreeBSD 4.6-PRERELEASE #1: Thu May 9 12:50:45 BST 2002 > : > :Only thing i've noticed is > :May 13 17:45:13 morrison /kernel: nfs server data1:/home: not responding > : > :Checked network connections and they are all ok, duplex correct etc and no > :firewall rules conflicting. > : > :Only thing is this box does have a Broadcom BCM5701 NIC in it which I know > :has had a few small issues.. > :bge0: mem 0xf7fb0000-0xf7fbffff irq 5 at device 5.0 on pci1 > : > :Any help greatly appreciated. > : > :thanks, > : > :-- > :Jamie Heckford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message