From owner-freebsd-questions@FreeBSD.ORG Tue Jan 11 14:10:40 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9758A16A4CE for ; Tue, 11 Jan 2005 14:10:40 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 555A743D45 for ; Tue, 11 Jan 2005 14:10:40 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 20717 invoked from network); 11 Jan 2005 14:10:39 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 Jan 2005 14:10:39 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id D86F644; Tue, 11 Jan 2005 09:10:38 -0500 (EST) Sender: lowell@be-well.ilk.org To: M References: <38228836-635C-11D9-9390-00039367611E@obmail.net> From: Lowell Gilbert Date: 11 Jan 2005 09:10:38 -0500 In-Reply-To: <38228836-635C-11D9-9390-00039367611E@obmail.net> Message-ID: <44brbwm4yp.fsf@be-well.ilk.org> Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: FreeBSD Mailing List Subject: Re: Odd kernel error on an NFS server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FreeBSD Mailing List List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2005 14:10:40 -0000 M writes: > I occasionally see this on an NFS server under heavy load > > ufs_rename: fvp == tvp (can't happen) > > Any idea what this means and where I should look to fix it? It means that somehow the UFS code got a request to rename a file to itself, and the kernel code didn't think it was possible for such a request to get into the kernel. [e.g., the mv(1) command checks for that before issuing the system call, so it can't happen that way] The error *is* handled cleanly, so it isn't necessarily a problem, but if you figure out what's causing it, preferably in a way that someone else can reproduce, please report it. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/