From owner-freebsd-stable Wed May 26 6:35:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 74ED514C4F; Wed, 26 May 1999 06:35:18 -0700 (PDT) (envelope-from Thierry.Herbelot@alcatel.fr) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA09773; Wed, 26 May 1999 14:32:37 +0200 Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id PAA06259; Wed, 26 May 1999 15:30:02 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with ESMTP id PAA24207; Wed, 26 May 1999 15:17:05 +0200 (MEST) Received: from telspace.alcatel.fr by telss1 (8.8.8+Sun/SMI-SVR4) id PAA07255; Wed, 26 May 1999 15:20:47 +0200 (MET DST) Message-ID: <374BF688.6295EE61@telspace.alcatel.fr> Date: Wed, 26 May 1999 15:26:33 +0200 From: Thierry Herbelot Reply-To: thierry.herbelot@alcatel.fr Organization: Alcatel CIT Nanterre X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.5.1 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: kent@erlang.ericsson.se Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Problem running NFS server References: <19990526145707M.kent@erlang.ericsson.se> Content-Type: multipart/mixed; boundary="------------DC665A64C7BBAA7C82152A68" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------DC665A64C7BBAA7C82152A68 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, Do you use NFS v3 with TCP (which is the default on Sun) ? If so, problems are to be expected : there was a thread on the subject on -Stable and one outcome was the recommendation to use rather UDP with NFS v3 (NFS on TCP may be better on FreeBSD v4.0-Current, but -Current should not be used for production servers - more explanations on this subject via a post by Daniel C. Sobral, dated Thu, 20 May 1999) TfH Kent Boortz wrote: > > I use FreeBSD 3.1 as an NFS server in an environment with almost > exclusively Solaris Sparc workstations. I needed an extra NFS server > for our "Daily Builds" so I grabbed an Dell Optiplex 264MHz PII with > 64 MB RAM and I put in an extra 7200 rpm 14 GB IDE disk to export > using NFS. It is connected with 100 Mbit ethernet to a switch. > > Problem is, it has problems working as an NFS server. The load is > heavy at time from up to three clients. But I expected a FreeBSD > system to deal with this at least as good as an old Ultra 1 > SparcStation that I used earlier as an NFS server. Could you give me > hints about what the problem can be and maybe what commands to use for > monitoring the problem? I include the "dmesg" output at the end of > this mail. > > The Solaris client get lots of "NFS server turkey not responding still > trying" and some /var/adm/messages > > NFS create failed for server turkey: error 11 (RPC: Server can't decode arguments) > NFS create failed for server turkey: error 9 (RPC: Program/version mismatch) > NFS lookup failed for server turkey: error 10 (RPC: Procedure unavailable) > NFS lookup failed for server turkey: error 11 (RPC: Server can't decode arguments) > NFS lookup failed for server turkey: error 7 (RPC: Authentication error) > NFS lookup failed for server turkey: error 8 (RPC: Program unavailable) > NFS lookup failed for server turkey: error 9 (RPC: Program/version mismatch) > > In the log file from one the daily builds there was two "I/O error" > writing to the NFS exported disk. The FreeBSD box has no /var/log/messages > that i can relate to this problems. > > The FreeBSD machine has also rebooted a couple of times with no trace > of the cause in the message log. It has also lost network contact a > couple of times requiring a reboot (I don't have details about the > state it was in, I was not the one rebooting it). No heavy load at the > time for the spontaneous reboots or lost contact. > > I suspect DMA is disabled from the dmesg output below, how do I enable it? > Can this be the problem? > > Is the 64MB memory the problem? > > Does the NFS errors above indicate ethernet card buffer overun? > > Is there incompatibilities between NFS clients on Solaris 2.5.1 and > the NFS server on FreeBSD 3.1? > > Or is FreeBSD 3.1 not stable enough? Should I switch to FreeBSD 2.X? > > Or is it really true that IDE sucks? ;-) > > /kgb > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.1-RELEASE #4: Thu Apr 29 14:12:04 CEST 1999 > root@scotch:/a/super/export/exec/x86.freebsd/src/sys/compile/CSLAB > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium II (264.89-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping=4 > Features=0x80f9ff > real memory = 67108864 (65536K bytes) > avail memory = 62291968 (60832K bytes) > Preloaded elf kernel "kernel" at 0xf02d8000. > Probing for devices on PCI bus 0: > chip0: rev 0x03 on pci0.0.0 > chip1: rev 0x03 on pci0.1.0 > chip2: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x01 on pci0.7.1 > chip3: rev 0x01 on pci0.7.3 > chip4: rev 0x03 on pci0.15.0 > xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.17.0 > xl0: Ethernet address: 00:c0:4f:91:6b:d4 > xl0: autoneg complete, link status good (full-duplex, 100Mbps) > Probing for devices on PCI bus 1: > vga0: rev 0x5c on pci1.0.0 > Probing for devices on PCI bus 2: > Probing for PnP devices: > CSN 1 Vendor ID: CSC6835 [0x3568630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] > mss_attach 1 at 0x530 irq 5 dma 1:0 flags 0x10 > pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa > Probing for devices on the ISA bus: > sc0 on isa > sc0: VGA color <16 virtual consoles, flags=0x0> > atkbdc0 at 0x60-0x6f on motherboard > atkbd0 irq 1 on isa > psm0 not found > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > pcm0 not probed due to drq conflict with pcm1 at 1 > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2): > wd2: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, dma, iordy > acd0: drive speed 2067 - 4134KB/sec, 128KB cache > acd0: supported read types: CD-R, CD-DA > acd0: Audio: play, 16 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > ppc0 at 0x378 irq 7 on isa > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > nlpt0: on ppbus 0 > nlpt0: Interrupt-driven port > ppi0: on ppbus 0 > plip0: on ppbus 0 > npx0 on motherboard > npx0: INT 16 interface > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > apm0 flags 0x31 on isa > apm: found APM BIOS version 1.2 > changing root device to wd0s1a > WARNING: / was not properly dismounted > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > ffs_mountfs: superblock updated for soft updates > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --------------DC665A64C7BBAA7C82152A68 Content-Type: text/x-vcard; charset=us-ascii; name="thierry.herbelot.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Thierry Herbelot Content-Disposition: attachment; filename="thierry.herbelot.vcf" begin:vcard n:Herbelot;Thierry tel;work:(+33) 1 46 52 47 23 x-mozilla-html:FALSE url:http://perso.cybercable.fr/herbelot org:CIT Nanterre adr:;;;;;; version:2.1 email;internet:thierry.herbelot@alcatel.fr x-mozilla-cpt:;-22032 fn:Thierry Herbelot end:vcard --------------DC665A64C7BBAA7C82152A68-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message