From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 11:44:51 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 78BD416A40F for ; Sun, 7 Jan 2007 11:44:51 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3922613C459 for ; Sun, 7 Jan 2007 11:44:51 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id EA9C98442F; Sun, 7 Jan 2007 12:44:49 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23387-09; Sun, 7 Jan 2007 12:44:45 +0100 (CET) Received: from [172.16.164.1] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 3D71884425; Sun, 7 Jan 2007 12:44:45 +0100 (CET) Message-ID: <45A0DD27.4020704@fsn.hu> Date: Sun, 07 Jan 2007 12:44:39 +0100 From: Attila Nagy User-Agent: Thunderbird 2.0b1 (Windows/20061206) MIME-Version: 1.0 To: perryh@pluto.rain.com References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> In-Reply-To: <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-hackers@freebsd.org 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: Sun, 07 Jan 2007 11:44:51 -0000 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. > Yes this would be very good, especially if this wouldn't be a production machine or if I could reproduce this on a test system. But neither of this are true. :( Maybe I will try it on a sleepless night, in the maintenance window, thanks for the idea.