From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 01:01:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B56FC16A403 for ; Thu, 11 Jan 2007 01:01:50 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id A038E13C46B for ; Thu, 11 Jan 2007 01:01:50 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7B33E1A4D8D; Wed, 10 Jan 2007 17:01:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E185F513F8; Wed, 10 Jan 2007 20:01:49 -0500 (EST) Date: Wed, 10 Jan 2007 20:01:49 -0500 From: Kris Kennaway To: Attila Nagy Message-ID: <20070111010149.GA2704@xor.obsecurity.org> References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> <45A0DD27.4020704@fsn.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <45A0DD27.4020704@fsn.hu> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 01:01:50 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 07, 2007 at 12:44:39PM +0100, Attila Nagy wrote: > On 2007.01.07. 1:11, perryh@pluto.rain.com wrote: > >It sounds as if the caller of ufs_rename() is confused. You could > >try setting a breakpoint on the printf(), or change it to a panic() > >to get a dump, and try to figure out who the caller is and what is > >going on. > > =20 > Yes this would be very good, especially if this wouldn't be a production= =20 > machine or if I could reproduce this on a test system. But neither of=20 > this are true. :( >=20 > Maybe I will try it on a sleepless night, in the maintenance window,=20 > thanks for the idea. Try forcing a fsck, sometimes bizarre FS panics are due to filesystem corruption. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (FreeBSD) iD8DBQFFpYx9Wry0BWjoQKURAh/tAJ0SOZOSS6zLBes+XllaLe+lyzf9bgCfdJxX Q0u5cg8FLKFFdCZr51ReOMU= =1qLH -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q--