From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 20:00:29 2006 Return-Path: X-Original-To: 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 7049916A41F; Fri, 6 Jan 2006 20:00:29 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCA4D43D46; Fri, 6 Jan 2006 20:00:28 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2ADA552C88; Fri, 6 Jan 2006 21:00:26 +0100 (CET) Received: from localhost (dkr191.neoplus.adsl.tpnet.pl [83.24.21.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D052950F92; Fri, 6 Jan 2006 21:00:16 +0100 (CET) Date: Fri, 6 Jan 2006 21:00:10 +0100 From: Pawel Jakub Dawidek To: Scott Long Message-ID: <20060106200009.GA53067@garage.freebsd.pl> References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <43BA9C5C.9010307@samsco.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 20:00:29 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: +> David O'Brien wrote: +>=20 +> >Just in case anyone thought the bug had been fixed... +> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 +> >panic: ufs_dirbad: bad dir +> >cpuid =3D 1 +> >KDB: stack backtrace: +> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e =3D = kdb_backtrace+0x2e +> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 =3D panic+0x= 128 +> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d =3D ufs_dirb= ad+0x4d +> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = =3D ufs_lookup+0x3ad +> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0= xc068cd4e =3D VOP_CACHEDLOOKUP_APV+0x9e +> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc05= 7275a =3D vfs_cache_lookup+0xca +> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 =3D= VOP_LOOKUP_APV+0xa6 +> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e =3D lookup+0x44e +> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf =3D namei+0x44f +> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd =3D kern_stat+0= x3d +> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f =3D stat+0x2f +> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 =3D syscall+0x323 +> >Xint0x80_syscall() at 0xc066d33f =3D Xint0x80_syscall+0x1f +>=20 +> Please include the console printf that is right about the panic message. +> It will say either something about a mangled entry or an isize too +> small. Since this problem is happening consistently for you, but there +> seem to be no other problem reports from others, I'd highly suspect that +> you have filesystem damage that isn't getting detected by fsck. I assum= e that you are running fsck in the foreground and not in the background, ye= s? The easiest solution=20 +> here might be to figure out which +> directory is causing the problem, and just clri its inode and then clean +> up the mess. I'm able to reproduce it with newly newfs(8)ed file system: /mnt: bad dir ino 17382405 at offset 0: mangled entry panic: ufs_dirbad: bad dir KDB: enter: panic [...] db> tr =20 Tracing pid 427 tid 100057 td 0xc7ccaa80 kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup+0x39f VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at VOP_C= ACHEDLOOKUP_APV+0xc4 vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0xc8 VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x28176efb, esp =3D 0xbfbf= e90c, ebp =3D 0xbfbfea48 --- --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvsxJForvXbEpPzQRAju3AJwLmWmSNIi5PpkON09wtLlaGvZgcgCfVkbd QPAGBcCIQ2q0PfVrabWLqp8= =dY0H -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU--