From owner-freebsd-current Sun Jun 10 9:36:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id B90FA37B403 for ; Sun, 10 Jun 2001 09:36:42 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.3/8.11.3) with SMTP id f5AGZgf30742; Sun, 10 Jun 2001 12:35:43 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 10 Jun 2001 12:35:41 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Joerg Wunsch Cc: freebsd-current@freebsd.org Subject: Re: panic: ufs_extattr_uepm_destroy: not initialized In-Reply-To: <200106092219.f59MJNI85937@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 10 Jun 2001, Joerg Wunsch wrote: > Joerg Wunsch wrote: > > > It /only/ happens after a "mount -a", not after just mounting /tmp > > only. No idea why, the only `obscure' filesystems i've got are procfs > > and portalfs. > > portalfs indeed seems to be the culprit for leaving an unreferenced file > in /tmp. However, the panic for forcibly umounting /tmp then clearly > belongs to the extattr code. Removed the option from my config again (i > just wanted to give ACLs a try only anyway), and now i'm living without > that panic again. Thomas Moestl recently committed some fixes to the EA code, and may have a couple more in the pipeline that address these problems. Out of curiosity, does your /tmp actually have EA's started on it, or is it just the kernel option? Are you using MFS or ext2fs at all? (I've only recently started recovering from moving, so I'm fairly behind on -CURRENT e-mail) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message