Date: Fri, 25 Jan 2002 18:50:08 -0600 From: Doug Swarin <doug@staff.texas.net> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org, bright@mu.org, sobomax@freebsd.org, kris@obsecurity.org, re@freebsd.org Subject: Re: Panic in ufs_dirbad() Message-ID: <20020125185007.A64746@staff.texas.net> In-Reply-To: <Pine.NEB.3.96L.1020125194709.80112G-100000@fledge.watson.org>; from rwatson@freebsd.org on Fri, Jan 25, 2002 at 07:48:09PM -0500 References: <20020125184512.A64502@staff.texas.net> <Pine.NEB.3.96L.1020125194709.80112G-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 25, 2002 at 07:48:09PM -0500, Robert Watson wrote: > > On Fri, 25 Jan 2002, Doug Swarin wrote: > > > I have actually seen this panic very recently on -STABLE. Matt Dillon > > suspected an issue with the RAID controller I was using (aac) after some > > debugging work. > > > > I am still waiting on the results of diagnostic testing on the RAID > > controller, but I just wanted to offer an additional data point. > > > > I have attached dmesg and some of the results of our debugging session > > below. The panic occurred during heavy file create/delete activity. I > > referred to PR kern/13150, which may or may not be related. > > > > We determined that *ep in ufs_lookup contained garbage (from a file > > name). ep->d_name contained file data. > > Alternatively, if it's only recent -STABLE, maybe it's something to do > with the recent enabling of UFS_DIRHASH in -STABLE by default? If so, > this might require immediate action before 4.5-RELEASE goes out the door > (very, very soon). Has anyone managed to track it down anymore? I do not have UFS_DIRHASH enabled in my kernel. -- Doug Swarin, Programmer doug (at) texas dot net 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?20020125185007.A64746>