From owner-freebsd-current@FreeBSD.ORG Thu Nov 25 18:16:36 2004 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 D1A9C16A4CE for ; Thu, 25 Nov 2004 18:16:36 +0000 (GMT) Received: from fed1rmmtao12.cox.net (fed1rmmtao12.cox.net [68.230.241.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89D6B43D3F for ; Thu, 25 Nov 2004 18:16:36 +0000 (GMT) (envelope-from housel@acm.org) Received: from housel.dyndns.org ([68.4.109.244]) by fed1rmmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041125181636.FLSZ3296.fed1rmmtao12.cox.net@housel.dyndns.org> for ; Thu, 25 Nov 2004 13:16:36 -0500 Received: (from housel@localhost) by housel.dyndns.org (8.13.1/8.13.1/Submit) id iAPIGREb018570 for freebsd-current@freebsd.org; Thu, 25 Nov 2004 10:16:27 -0800 (PST) (envelope-from housel@acm.org) X-Authentication-Warning: housel.dyndns.org: housel set sender to housel@acm.org using -f From: "Peter S. Housel" To: freebsd-current@freebsd.org In-Reply-To: <200411022243.02175.mistry.7@osu.edu> References: <20041031161538.GA989@naboo.wanadoo.fr> <200411022243.02175.mistry.7@osu.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 25 Nov 2004 10:16:26 -0800 Message-Id: <1101406586.938.3.camel@housel.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Subject: Re: panic: Wrong vnode in bufstrategy(bp=0xc5e058c0, vp=0xc1615238) 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: Thu, 25 Nov 2004 18:16:37 -0000 On Tue, 2004-11-02 at 22:43 -0500, Anish Mistry wrote: > On Sunday 31 October 2004 11:15 am, Aurelien Nephtali wrote: > > Hello, > > > > Since the recent commits by phk@, I can't mount any NTFS file system > > without getting a : > > > > panic: Wrong vnode in bufstrategy(bp=0xc5e058c0, vp=0xc1615238) > > > > > > Trace output as well as dmesg output are attached. > > > > Thanks! > Just wanted to add a me too. I can post my back trace too if it would > help. Just wanted to add that I'm still seeing this on my system, cvsupped two days ago. I can mount NTFS, but reading files from it locks up the system hard with nothing but the 1-line panic message. -Peter-