From owner-freebsd-questions@FreeBSD.ORG Thu Jan 6 15:50:05 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31F1616A4CE for ; Thu, 6 Jan 2005 15:50:05 +0000 (GMT) Received: from antsrv1.ant.uni-bremen.de (antsrv2.ant.uni-bremen.de [134.102.176.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAC5B43D54 for ; Thu, 6 Jan 2005 15:50:03 +0000 (GMT) (envelope-from rebehn@ant.uni-bremen.de) Received: from bremerhaven.ant.uni-bremen.de ([134.102.176.10]) by antsrv2.ant.uni-bremen.de with esmtp (Exim 4.42) id 1CmZtc-0004Go-It; Thu, 06 Jan 2005 16:49:56 +0100 Message-ID: <41DD5E24.905@ant.uni-bremen.de> Date: Thu, 06 Jan 2005 16:49:56 +0100 From: Heinrich Rebehn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041124 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erik Norgaard References: <41DD5618.6070801@locolomo.org> In-Reply-To: <41DD5618.6070801@locolomo.org> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "antsrv2.ant.uni-bremen.de", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.systemnfs2 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Tue Jan 4 >> 19:14:40 EST 2005 root@nfs2:/usr/obj/usr/src/sys/NFS i386 >> >> Two CPUs (tried hyperthreading and not), 4 GB of memory >> >> CPU: Intel(R) Xeon(TM)= 0xf29 Stepping = 9 >> >> Features=0xbfebfbff> ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HT >> 4160225280 (3967 MB) >> avail memory = 4073271296 (3884 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> cpu0 (BSP): APIC ID: 0 >> Q-Logic FC card >> >> isp0: port pci3but48%a hard lock and no >> error messages in /var/log/messages or on the screen. I've moved all >> the disks to a duplicate system. If it> > See this message from yesterday (submitted to announce): > > ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:01.nfs.asc > > In short, update your system. > > Cheers, Erik [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description -------------------------------------------------- cc: M cc: freebsd-questions@freebsd.org Subject: Re: SMP and NFS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2005 15:50:05 -0000 Erik Norgaard wrote: > M wrote: > >> I have a system that is being used as a high performance NFS server >> >> FreeBSD nfs2 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #1: Tue Jan 4 >> 19:14:40 EST 2005 root@nfs2:/usr/obj/usr/src/sys/NFS i386 >> >> Two CPUs (tried hyperthreading and not), 4 GB of memory >> >> CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2400.10-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 >> >> Features=0xbfebfbff> ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HT >> T,TM,PBE> >> Hyperthreading: 2 logical CPUs >> real memory = 4160225280 (3967 MB) >> avail memory = 4073271296 (3884 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 6 >> >> The NFS exported filesystem is on a Q-Logic FC card >> >> isp0: port 0x4000-0x40ff mem >> 0xf8300000-0xf8300fff irq 28 at device 3.0 on pci3 >> isp0: [GIANT-LOCKED] >> >> The disk is formated UFS2 and is big, but not *that* big yet >> >> /dev/da1s1d 471860682 206516934 227594894 48% /usr/local/export >> >> Every 12 hours or so the system crashes with a hard lock and no >> error messages in /var/log/messages or on the screen. I've moved all >> the disks to a duplicate system. If it continues to lock hard what's >> the possibility the issue is SMP? > > > See this message from yesterday (submitted to announce): > > ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:01.nfs.asc > > In short, update your system. > > Cheers, Erik Since i am going to set up a SMP NFS server too, i would be interested if this really solves the OP's problem. After all, he is talking about a "hard lock with no messages..", as opposed to a "kernel panic", which in my understanding always produces messages. Heinrich Rebehn University of Bremen Physics / Electrical and Electronics Engineering - Department of Telecommunications - Phone : +49/421/218-4664 Fax : -3341