From owner-freebsd-current@FreeBSD.ORG  Sat Feb 12 17:42:47 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 7A28C16A4D5
	for <freebsd-current@freebsd.org>;
	Sat, 12 Feb 2005 17:42:47 +0000 (GMT)
Received: from relay1.ntu-kpi.kiev.ua (noc.ntu-kpi.kiev.ua [195.245.194.34])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 59A5343D31
	for <freebsd-current@freebsd.org>;
	Sat, 12 Feb 2005 17:42:46 +0000 (GMT)
	(envelope-from edd@ntu-kpi.kiev.ua)
Received: by relay1.ntu-kpi.kiev.ua (Postfix, from userid 2000)
	id 2C6BF17BDB0; Sat, 12 Feb 2005 19:42:43 +0200 (EET)
Date: Sat, 12 Feb 2005 19:42:43 +0200
From: Edward Melnik <edd@edd.kiev.ua>
To: freebsd-current@freebsd.org
Message-ID: <20050212174243.GA77809@noc.ntu-kpi.kiev.ua>
References: <20050211121215.GC14427@reed.uran.net.ua>
	<20050211190653.P40433@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-u
Content-Disposition: inline
In-Reply-To: <20050211190653.P40433@carver.gumbysoft.com>
User-Agent: Mutt/1.5.6i
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 17:42:47 -0000

On Fri, Feb 11, 2005 at 07:08:16PM -0800, Doug White wrote:
> 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...
> 

yea. Problem is solved. Thanks.

-- 
Edward Melnik.