From owner-freebsd-current@FreeBSD.ORG  Sat Feb 12 03:08:19 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 310F216A4CE
	for <freebsd-current@freebsd.org>;
	Sat, 12 Feb 2005 03:08:19 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1926B43D39
	for <freebsd-current@freebsd.org>;
	Sat, 12 Feb 2005 03:08:17 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 07F2D72DD4; Fri, 11 Feb 2005 19:08:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 027F772DCB;
	Fri, 11 Feb 2005 19:08:17 -0800 (PST)
Date: Fri, 11 Feb 2005 19:08:16 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Edward Melnik <edd@edd.kiev.ua>
In-Reply-To: <20050211121215.GC14427@reed.uran.net.ua>
Message-ID: <20050211190653.P40433@carver.gumbysoft.com>
References: <20050211121215.GC14427@reed.uran.net.ua>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: [q] scsi disks  or what the problem?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Feb 2005 03:08:19 -0000

On Fri, 11 Feb 2005, Edward Melnik wrote:

> Hello!
>
> My server paniced with:
>
> panic: ufs_dirbad: bad dir
> cpuid = 0;
> boot() called on cpu#0

I'd suggest booting single-user and fscking all filesystems. (fsck -y -a)
It appears to be disk data corruption...

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org