From owner-freebsd-current Tue Oct 29 19:42:56 2002 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 7C3CD37B401 for ; Tue, 29 Oct 2002 19:42:54 -0800 (PST) Received: from power.doogles.com (power.doogles.com [209.15.149.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id C55E743E7B for ; Tue, 29 Oct 2002 19:42:53 -0800 (PST) (envelope-from jyoung@power.doogles.com) Received: from localhost (jyoung@localhost) by power.doogles.com (8.11.6/8.11.6) with ESMTP id g9U3gkd18082; Tue, 29 Oct 2002 21:42:46 -0600 Date: Tue, 29 Oct 2002 21:42:46 -0600 (CST) From: "Jason A. Young" To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP! GEOM as default in 5 days... In-Reply-To: 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 Not sure if a fix was ever implemented for this problem directly, but I thought I'd note that the problem I experienced mounting my NTFS partition has gone away. I hadn't tried it for a while, so I don't know the exact date/commit that did the deed. Thanks! -- Jason Young, CCIE #8607, MCSE Sr. Network Technician, WAN Technologies (314)817-0131 http://www.wantec.com On Wed, 16 Oct 2002, Jason A. Young wrote: > > Attempting to mount my Win2K NTFS partition on my laptop after the > introduction of GEOM results in immediate 100% reproduceable panics. I > built GEOM into my kernel the day after it was introduced into CVS, and > none of the commits made since seem to have fixed it. > > I apologize for not posting my panic messages earlier, but the machine > ends up in a state where it can't save a core and I haven't got a > null-modem cable for a serial console handy. I decided to go ahead and > transcribe this by hand, so there will likely be typos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message