From owner-freebsd-bugs Mon Nov 16 06:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15334 for freebsd-bugs-outgoing; Mon, 16 Nov 1998 06:27:40 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA15327 for ; Mon, 16 Nov 1998 06:27:30 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id JAA07684; Mon, 16 Nov 1998 09:31:53 -0500 From: Bill Paul Message-Id: <199811161431.JAA07684@skynet.ctr.columbia.edu> Subject: Re: kern/8703: NFS Freezes when copying files from 3.0 to earlier release To: n@nectar.com Date: Mon, 16 Nov 1998 09:31:51 -0500 (EST) Cc: don@wtech.com, bugs@FreeBSD.ORG In-Reply-To: <199811160650.WAA14453@freefall.freebsd.org> from "Jacques Vidrine" at Nov 15, 98 10:50:01 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of all the gin joints in all the towns in all the world, Jacques Vidrine had to walk into mine and say: > The following reply was made to PR kern/8703; it has been noted by GNATS. > > From: Jacques Vidrine > To: don@whtech.com > Cc: freebsd-gnats-submit@FreeBSD.ORG, wpaul@FreeBSD.ORG > Subject: Re: kern/8703: NFS Freezes when copying files from 3.0 to earlier release > Date: Mon, 16 Nov 1998 00:43:06 -0600 > > I assume you mean 2.2.7, not 2.7. > > I cannot reproduce this problem using a 3.0-CURRENT and > 2.2-STABLE machine, but I don't have RealTek cards with which > to test. Perhaps the rl driver author may have some insight. > > Can you replace the RealTek card with some other supported > card and test, so that we can determine if the driver/card > is part of the trouble? Given a choice between blaming the RealTek driver and blaming NFS, I'd be more inclined to blame NFS. I have also had problems with NFS in 3.0-RELEASE, except I was using 3.0-RELEASE on both the client and server. Mounting filesystems worked fine. Reading files worked fine. But trying to write files to the server would wedge and leave a 0-byte file behind. This is with a 3Com 3c905B card, not a RealTek. This problem cropped up in a lab full of machines and I needed to fix it quickly, so I grabbed the November 3rd 3.0-SNAP kernel sources and build a kernel from them with the same kernel configuration I used for 3.0-RELEASE, and it worked without any problems. So please try me this: - FTP to current.freebsd.org, and get the source code for the kernel from the November 3rd 3.0 SNAP (grab the ssys.?? files, and do: cat ssys.* | gzip -d | tar -xvf -) - also get the source code for the config(1) command (this is actually part of the usrsbin tarball; I think it's safe to cheat by swiping the source directly from the /pub/FreeBSD/FreeBSD-current/src/usr.sbin directory from ftp.freebsd.org) - Compile a kernel from these sources and test it. See if the problem persists. If that works, you may want to do a complete install of the SNAP in place of 3.0-RELEASE. There also seems to be a November 16th SNAP now (about time they got that working again) which you can test if you're feeling adventurous. The RealTek driver is rather simpleminded, just like the RealTek card itself. There's not really much that can go wrong with it. Also, if you can still ping or telnet to the server when your NFS problem manifests, the card is still working. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message