From owner-freebsd-hackers  Sun Mar 28  8:45:17 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133])
	by hub.freebsd.org (Postfix) with ESMTP id BA826152EE
	for <hackers@FreeBSD.ORG>; Sun, 28 Mar 1999 08:45:14 -0800 (PST)
	(envelope-from bright@rush.net)
Received: from localhost (bright@localhost)
	by cygnus.rush.net (8.9.3/8.9.3) with SMTP id LAA15762;
	Sun, 28 Mar 1999 11:53:25 -0500 (EST)
Date: Sun, 28 Mar 1999 11:53:24 -0500 (EST)
From: Alfred Perlstein <bright@rush.net>
To: Darren Reed <avalon@coombs.anu.edu.au>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>, hackers@FreeBSD.ORG
Subject: Re: another ufs panic..
In-Reply-To: <199903281635.CAA21317@cheops.anu.edu.au>
Message-ID: <Pine.BSF.3.96.990328114948.4169k-100000@cygnus.rush.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 29 Mar 1999, Darren Reed wrote:

> 
> whilst I was sitting here, doing a copy using rsync:
> 
> /mnt/usr: bad dir ino 69912 at offset 88: mangled entry
> panic: bad dir

I think you have enough explanations now to fix the problem:

1) your scsi setup is bad
2) you have an _still_ undetermined old version of freebsd
   what version are you even using?

#1 commonly causes the baddir panic, i've seen it before on
bogus scsi setups.  violating a spec and then stressing
the system is a good way to generate a panic.
If i ran 100bT for several hundred feet over the spec and
then complained about freebsd dropping packets.....

#2 there's prolly an update out there

-Alfred

> 
> darren
> 
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message