From owner-freebsd-current@FreeBSD.ORG Fri Jun 6 14:25:31 2003 Return-Path: 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 DF66E37B401 for ; Fri, 6 Jun 2003 14:25:31 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC54743FA3 for ; Fri, 6 Jun 2003 14:25:30 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h56LOFOn099191; Fri, 6 Jun 2003 17:24:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h56LOFlZ099188; Fri, 6 Jun 2003 17:24:15 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 6 Jun 2003 17:24:14 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Daniel C. Sobral" In-Reply-To: <3EE0F6CA.9070204@tcoip.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: CURRENT Subject: Re: PANIC: FreeBSD dislikes temps (panic when mounting /tmp) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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 Jun 2003 21:25:32 -0000 On Fri, 6 Jun 2003, Daniel C. Sobral wrote: > Robert, I cc'ed you because you are usually guilty anyway... (besides, > there's a ea thingy there :) I probably am, actually :-). Is the file system in question UFS or UFS2? To summarize the context of the crash: when UFS_EXTATTR_AUTOSTART is present in the kernel, UFS file systems are scanned for a ".attribute" directory in the root of the file system, and then it walks into various subdirectories of that directory looking for attribute files to start. This happens fairly early in the mount process, and it looks like the panic is in the UFS_DIRHASH code, so perhaps we're bumping into an incompletely initialized inode field of some sort. I'll look in detail at this over the weekend. Is this during the boot, or is this later when you mount a UFS file system? The trace is truncated at the bottom, I think. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories