Date: Wed, 28 Jul 1999 19:35:43 -0400 (EDT) From: Bill Paul <wpaul@skynet.ctr.columbia.edu> To: dillon@apollo.backplane.com (Matthew Dillon) Cc: current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm Message-ID: <199907282335.TAA15438@skynet.ctr.columbia.edu> In-Reply-To: <199907282257.PAA64091@apollo.backplane.com> from "Matthew Dillon" at Jul 28, 99 03:57:51 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > > Ok, so if I understand this correctly you have a FreeBSD server and > an IRIX client. UDP mounts work, TCP mounts do not. You are using > the AMD automounting software running on the ... client I presume? > It is the server that is panicing. Yes. But it's nothing to do with AMD. I can do it manually: irix# mount -o vers=3,proto=tcp freebsd:/usr /mnt irix# cd /mnt; du FreeBSD box explodes. > First of all, if these are production machines stick with UDP so's > you don't tear your hair out. Also double check that the bug still > exists with the absolute latest CURRENT if you can. I'd love to except *somebody* hasn't gotten arround to fixing current.freebsd.org yet. *Nudges jkh* And I'm not going to stick with UDP mounts because that's hiding the problem, not fixing it. You're just going to get more grief from the next poor fool who runs afoul of this problem. > Also please run this (on the FreeBSD server running CURRENT). It > will tell me whether NFS is being forced to realign packet data > coming from your ethernet controller. (In the example below, my > NFS server has to realign the data). > > # sysctl -a | fgrep nfs > vfs.nfs.realign_test: 1583064 > vfs.nfs.realign_count: 1583064 In the case of the 4.0 box, it explodes almost immediately: there's no chance to actually obtain this data there. I added some printfs to the 3.2 box briefly and it didn't look like the realign code was being triggered. > We fixed a serious data corruption bug with NFSv3 over TCP that > could result in panics. This fix was made on May 2nd to current > and MFC'd to stable on May 8th. This fix made it into 3.2. FreeBSD mcmillan.ctr.columbia.edu 4.0-19990715-CURRENT FreeBSD 4.0-19990715-CURRENT #2: Tue Jul 20 17:07:35 EDT 1999 operator@mcmillan.ctr.columbia.edu:/usr/src/sys/compile/TEST i386 Should be in there. I don't think that's it. Note that the 'mbuf siz' value that gets printed is the exactly the same every time. -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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907282335.TAA15438>