Date: Mon, 1 Jun 1998 23:00:54 -0400 (EDT) From: Scott Drassinower <scottd@cloud9.net> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: misc/6824: Intel EtherExpress 100+, 2.2.6 NFS troubles Message-ID: <199806020300.XAA04725@earl-grey.cloud9.net>
next in thread | raw e-mail | index | archive | help
>Number: 6824 >Category: misc >Synopsis: Intel EtherExpress 100+, 2.2.6 NFS troubles >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 1 20:10:01 PDT 1998 >Last-Modified: >Originator: Scott Drassinower >Organization: Cloud 9 Consulting, Inc. >Release: FreeBSD 2.2.6-RELEASE i386 >Environment: A network of 2.2.6 machines, all with Intel EtherExpress 100+ cards running at 100 megabit/full duplex, attached to a Cisco Catalyst 2900XL Ethernet switch. Various directories are shared via nfs between the machines. >Description: Some operations across nfs (like tail -f, or grep) with large files that can be updated while the process is running (like a log file) will eventually hang and become stuck in disk wait on the client. >How-To-Repeat: tail -f / grep / sz a large file that is getting regularly updated on the server (maillog, access_log, etc). When running at 100 megabit/full duplex on the switch, the process will eventually hang. Other operations on the mount are fine. Running the network at 10 megabit/half duplex (on a hub) won't cause this problem. >Fix: There is no workaround except for running at 10 megabits/half duplex. I have tried various combinations of read/write data sizes with mount_nfs (-r and -w on the client, at 1024 and 4096), as well as TCP transport (-T) and still can't eliminate this problem. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806020300.XAA04725>