From owner-freebsd-performance@FreeBSD.ORG Wed May 16 16:20:29 2007 Return-Path: X-Original-To: freebsd-performance@freebsd.org Delivered-To: freebsd-performance@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7405916A400 for ; Wed, 16 May 2007 16:20:29 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id D4D7213C45D for ; Wed, 16 May 2007 16:20:28 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from exchange-2.sandvine.com ([192.168.16.12]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 16 May 2007 12:08:25 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Wed, 16 May 2007 12:08:24 -0400 Message-ID: <5230D3C40B842D4F9FB3CD368021BEF72F08F1@exchange-2.sandvine.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ufs dead-locks on freebsd 6.2 Thread-Index: AceX1G4ru5sFcTfBQyOVPtiqpV6KBw== From: "Andrew Edwards" To: X-OriginalArrivalTime: 16 May 2007 16:08:25.0272 (UTC) FILETIME=[6EE52380:01C797D4] Subject: Ufs dead-locks on freebsd 6.2 X-BeenThere: freebsd-performance@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Performance/tuning List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2007 16:20:29 -0000 I have a system running a dual intel zeon 2.8Ghz with 4G of ram and using an intel raid controller model SRCU42X which uses the amr driver. I have had this server running 5.4 upgraded to 6.2 and was running fine for several months and then after a normal reboot I've started having all sorts of problems with what appears to be dead-locks in the filesystem. This server is my backup server and I rsync files from various servers onto this one fairly non-stop. If I stop the rsync's the system appears to be stable although I did have a kernel core just last night. When I have been able to observe the problem I ususally see one filesystem become inaccessible, perhaps var but I'm not sure, and then in a short period of time the whole system is inaccessible. Usually if I startup just one of the rsync's within a couple of hours the system will be un-usable. I did find this thread which seems to describe similar issues but this is a different driver. http://lists.freebsd.org/pipermail/freebsd-questions/2006-August/127835. html Currently I'm running with debug.mpsafevfs=3D0, debug.mpsafenet=3D1and debug.mpsafevm=3D0 but this doesn't seem to help. On perahps a related issue I have two other nearly identical systems which were going to be upgrading to 6.2 as on 5.4 I am experiencing deadlocks and when I hit ctrl-t I see the system is either stuck in ufs or zoneinfo and I have not found very much information about zoneinfo. Does anyone have any suggestions on what I can look for or other tuning options or had similar experiences?