From owner-freebsd-current@FreeBSD.ORG Tue Aug 3 01:51:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DF2716A4CF; Tue, 3 Aug 2004 01:51:38 +0000 (GMT) Received: from av3-2-sn4.m-sp.skanova.net (av3-2-sn4.m-sp.skanova.net [81.228.10.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB5B943D49; Tue, 3 Aug 2004 01:51:37 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av3-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 1E71237FD0; Tue, 3 Aug 2004 03:51:37 +0200 (CEST) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av3-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 0D15937FCE; Tue, 3 Aug 2004 03:51:37 +0200 (CEST) Received: from gadget (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id E133537E44; Tue, 3 Aug 2004 03:51:36 +0200 (CEST) From: "Daniel Eriksson" To: "'Scott Long'" Date: Tue, 3 Aug 2004 03:51:44 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <410EEAC8.8010900@freebsd.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 cc: 'freebsd current' Subject: RE: Panic in today's current, UFS problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Aug 2004 01:51:38 -0000 Scott Long wrote: >> What I did: >> 1. fdisk/label two 250GB discs hooked up to the on-board SATA=20 >> controller (using sysinstall) 2. copy ~20GB of data to both discs > > Is this step necessary in order to produce the panic? I have no idea. >> 3. successfully run the stress-test mentioned in Ville-Pertti=20 >> Keinonen's mail (above) > > Is this step necessary also? Again, no idea. >> 4. unmount both discs >> 5. run "atacontrol create RAID0 128 ad20 ad22" (the two SATA discs) = 6.=20 >> fdisk/label the striped array (using sysinstall, forcing it to UFS1)=20 >> 7. mount the new partition, and create three empty dirs 8. *boom* >>=20 > > How reproducable is this, and does it always panic in the same spot?=20 > There is definitely some sort of buffer corruption going on, and = either=20 > it's happening in the buffer/cache layer or it's a bad DMA from the = drive. Considering how much problems I've had with this machine lately I would = not at all be suprised if the error is somewhere else. The machine is unfortunately a production machine, and trying to reproduce panics (with = the risks associated with that, such as corrupted user data) is not really = an option. What I've done now is restart the server and run a newfs on the ataraid array of the two SATA discs. I'm in the process of copying 400+GB of = data onto that array, and will run some more stress-tests to verify its stability. So far (200GB into the copy-operation) everything looks good. /Daniel Eriksson