Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!news.netspace.net.au!news.mira.net.au!news.vbc.net!vbcnet-west!knews.uk0.vbc.net!vbcnet-gb!azure.xara.net!xara.net!news.maxwell.syr.edu!feed1.news.erols.com!newsfeeds.sol.net!ix.netcom.com!fortress.broadcom.com!scorpion.broadcom.com!usenet From: jsin@scorpion.broadcom.com (John Sin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Help with FreeBSD 2.2.2-RELEASE NFS/automounter problem Date: 2 Jun 1997 21:08:17 -0700 Organization: Broadcom Corporation Lines: 49 Message-ID: <5n05bh$2ci$1@scorpion.broadcom.com> NNTP-Posting-Host: scorpion.broadcom.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42138 Hi, I just converted one of my file server from FreeBSD 2.1.0-RELEASE to 2.2.2-RELEASE - it seems to have lots of enhancements and I like it a lot in general, but I have encountered a rather severe NFS problem. On my file server, I export the filesystem /d0 to other remote systems. Those remote systems mount it as /u/disk0; in fact, I run automounter on all my machines so that the file server's /d0 filesystem can always be refered to as /u/disk0, even when I'm logged on the server itself. This enables me to keep the home directory paths same on all machines; I have been doing things this way for several years w/o any problems, until last week. After I upgraded the server to 2.2.2-RELEASE, I see the following problem: 1. login to the file server 2. copy some moderate size (5MB?) file to /d0, from anywhere (local or networked partition). this works as expected. 3. now, copy the same moderate sized file to /u/disk0, from anywhere. this hangs the system - "NFS server hostname:/d0 not responding" Here is how I start amd: amd -a /tmp_mnt -c 1800 -k i386 -d broadcom.com -l syslog /u /etc/amd.map /etc/amd.map contains: disk0 type:=nfs;rhost:=hostname;rfs:=/d0 I'm using the vx0 driver (3c595 and with 3c905; at 10BaseT and at 100BaseTX). I haven't tested it with any other ethernet card, but I suspect that it won't matter much. I will try and confirm this tomorrow. All other aspects of NFS and amd appears to be OK -- it's only when I take the local filesystem and mount it via NFS through amd that I have problems. This worked OK on my 2.1.0-RELEASE and 2.1.5-RELEASE systems. One other things - I've noted that once the system hangs, and I leave the system alone long enough (about an hour or two?), it eventually panics with the error "out of mbuf clusters - increase maxusers!". This is strange since my MAXUSERS is currently set to 128. I would've thought that that is large enough. I thought I'd mention this; maybe it will be helpful in finding the source of the problem. At the moment, I've resorted to removing all references to local drives in /etc/amd.map -- this is obviously not desirable and I might have to consider down-grading to 2.1.5-RELEASE if I can't find a better solution soon. Any help/pointers will be much appreciated!