Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Mar 1998 09:36:48 -0800 (PST)
From:      Manfred Antar <root@mantar.slip.netcom.com>
To:        Karl Denninger <karl@mcs.net>
Cc:        current@FreeBSD.ORG, toor@dyson.iquest.net
Subject:   Re: panic ufs_dirbad
Message-ID:  <Pine.BSF.3.96.980328093107.2342A-100000@mantar.slip.netcom.com>
In-Reply-To: <Pine.BSF.3.96.980325175508.550B-100000@mantar.slip.netcom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Mar 1998, Manfred Antar wrote:

> On Wed, 25 Mar 1998, Karl Denninger wrote:
> 
> > On Wed, Mar 25, 1998 at 05:32:45PM -0800, Manfred Antar wrote:
> > > On Wed, 25 Mar 1998, Karl Denninger wrote:
> > > 
> > > > On Wed, Mar 25, 1998 at 05:21:47PM -0800, Manfred Antar wrote:
> > > > > On Wed, 25 Mar 1998, Karl Denninger wrote:
> > > > > 
> > > > > > What is the extract date on the sources in your kernel?
> > > > > > 
> > > > > March 24 6 p.m. pacific
> > > > > 	Today:
> > > > > I just did a make world today without having /usr/obj on a seperate
> > > > > partition. I rebooted and did fsck on /usr , no problems.
> > > > > For the past couple of days I have been doing make world's with
> > > > > /usr/obj on it's own partition (same disk) some complete some lock up.
> > > > > but every time /usr/obj is corupted with bad dirs (usually just one).
> > > > > I'm wondering if I have a bad disk, it's a brand new quantum Atlas 4.3
> > > > > gig ?
> > > > > 
> > > > > Manfred
> > > > 
> > > > Hmmmm... did you used to have a kernel on that machine from the "bad" time?
> > > > 
> > > Yes 
> > > It got so bad that I had to low level format it. Then restore off of tape 
> > > from Mar 10. The tape I used was from another disk a 4.1 gig seagate.
> > > Manfred
> > 
> > Well, I'm seeing the "tulip" panic and one in some of the ffs routines with
> > a current kernel from today right now.
> > 
> I have a cvs tree on another disk I think I'll build a kernel from the
> 12th and see what happens.
> Manfred
> 
> 
I think my problems might be controller related.
I was using a DPT 2124 caching raid (no raid) controller when I had these
problems. I swithched back to a Adaptec 2940 and no more bad_dir.
This is after a current make world with a current kernel.
Without fail i would get bad_dir with the DPT.
(/root)537}fsck /dev/sd0s1g
** /dev/rsd0s1g
** Last Mounted on /usr/obj
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
14660 files, 146387 used, 52208 free (128 frags, 6510 blocks, 0.1%
fragmentation)

Manfred
==============================
||    mantar@netcom.com     ||
||    Ph. (415) 681-6235    ||
==============================


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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980328093107.2342A-100000>