From owner-freebsd-stable@FreeBSD.ORG Wed Nov 29 11:54:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C45F16A403 for ; Wed, 29 Nov 2006 11:54:37 +0000 (UTC) (envelope-from freebsd-stable@epcdirect.co.uk) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 666DD43C9D for ; Wed, 29 Nov 2006 11:54:32 +0000 (GMT) (envelope-from freebsd-stable@epcdirect.co.uk) Received: from lfarr (unknown [195.10.240.21]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 2F1176C8821; Wed, 29 Nov 2006 11:54:33 +0000 (GMT) From: "Lawrence Farr" To: "'Kris Kennaway'" Date: Wed, 29 Nov 2006 11:54:33 -0000 Message-ID: <01d501c713ad$2308d5c0$750fa8c0@lfarr> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20061121210648.GA90974@xor.obsecurity.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 thread-index: AccNsfHF9BTnbMDFQJ2kYUn/Ee3HLwF+s7uA Cc: freebsd-stable@freebsd.org, 'Tom Samplonius' Subject: RE: ufs_dirbad: bad dir panic (Was Areca Weirdness) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2006 11:54:37 -0000 > -----Original Message----- > From: owner-freebsd-stable@freebsd.org > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Kris Kennaway > Sent: 21 November 2006 21:07 > To: Lawrence Farr > Cc: freebsd-stable@freebsd.org; 'Tom Samplonius'; 'Kris Kennaway' > Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness) > > On Tue, Nov 21, 2006 at 10:27:18AM -0000, Lawrence Farr wrote: > > > > > > > -----Original Message----- > > > From: Kris Kennaway [mailto:kris@obsecurity.org] > > > Sent: 21 November 2006 00:44 > > > To: Tom Samplonius > > > Cc: Kris Kennaway; freebsd-stable@freebsd.org; Lawrence Farr > > > Subject: Re: ufs_dirbad: bad dir panic (Was Areca Weirdness) > > > > > > On Mon, Nov 20, 2006 at 04:29:17PM -0800, Tom Samplonius wrote: > > > > > > > > ----- Kris Kennaway wrote: > > > > > > > > > >> If I newfs it, and copy data to it, I have > no problem > > > > > > > initially. > > > > > > I can repeat this 100% now, by copying data onto > the drive then > > > > > unmounting > > > > > > and remounting it. I have a core dump if anyone can > tell me what > > > > > info to > > > > > > get from it: > > > > > > > > > > > > Version String: FreeBSD 6.2-PRERELEASE #0: Wed Nov 15 > > > 19:57:01 GMT > > > > > 2006 > > > > > > > > > root@monitor.shorewood-epc.co.uk:/usr/obj/usr/src/sys/P6NOUSB > > > > > > Panic String: ufs_dirbad: bad dir > > > > > > > > > > Run fsck -fy on the filesystem, this is a common symptom of a > > > > > corrupted filesystem. > > > > > > > > I think the OP knows the filesystem is corrupted. The > > > problem is why does the filesystem get corrupted? The OP > > > says he can corrupt the filesystem on demand after a newfs. > > > So it could be the Areca driver, or even bad hardware. > > > > > > My point is that this panic can happen when your > filesystem becomes > > > corrupted, and the panic keeps happening during "normal" > filesystem > > > operations until you forcibly fsck it, at which point the > panic goes > > > away. > > > > > > Kris > > > > > > > I have been newfs'ing it and starting again, and it will > work once, but > > once unmounted and re-mounted it will panic with ufs_dirbad. > > OK, that's a different matter then. One thing you could try would be > to write known data directly to the device and then read it back or > verify the md5 sum and try to identify the failure mode. I'd try to > rule out hardware problems too. > > Kris > I made a volume that was under 2Tb and installed directly onto the Areca rather than the ATA drive. This has now run without issue for a week. Strangely, I did the same test on the ATA drive prior to this and it worked without issue for a week. Quite why it doesn't work with the ATA as the boot device and the Areca as storage is beyond me.