From owner-freebsd-current@FreeBSD.ORG Fri Jun 20 19:17:47 2003 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 F3ADC37B401 for ; Fri, 20 Jun 2003 19:17:46 -0700 (PDT) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 603F343F93 for ; Fri, 20 Jun 2003 19:17:46 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (210.50.200.57) by smtp02.syd.iprimus.net.au (7.0.015) id 3EED7970001ECCD4; Sat, 21 Jun 2003 12:17:44 +1000 Received: by dilbert.robbins.dropbear.id.au (Postfix, from userid 1000) id 9FE7BC91F; Sat, 21 Jun 2003 12:17:36 +1000 (EST) Date: Sat, 21 Jun 2003 12:17:36 +1000 From: Tim Robbins To: NAKAJI Hiroyuki Message-ID: <20030621121736.A46779@dilbert.robbins.dropbear.id.au> References: <8665n4j3v0.fsf@xa12.heimat.gr.jp> <8665n4j3v0.fsf@xa12.heimat.gr.jp> <20030620013558.A52145@dilbert.robbins.dropbear.id.au> <86he6k4xqi.fsf@xa12.heimat.gr.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <86he6k4xqi.fsf@xa12.heimat.gr.jp>; from nakaji@tutrp.tut.ac.jp on Fri, Jun 20, 2003 at 11:41:57PM +0900 cc: freebsd-current@freebsd.org Subject: Re: mount_ntfs causes panic 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: Sat, 21 Jun 2003 02:17:47 -0000 On Fri, Jun 20, 2003 at 11:41:57PM +0900, NAKAJI Hiroyuki wrote: > >>>>> In <20030620013558.A52145@dilbert.robbins.dropbear.id.au> > >>>>> Tim Robbins wrote: > > > > /etc/fstab: > > > /dev/ad0s2 /mnt/winnt ntfs ro,noauto 0 0 > > > > > > When "mount /mnt/winnt", the system falls into DDB. > > > This looks like a bug in the buffer cache code. I'm working on > > trying to fix it. Mounting read-write instead of read-only ought to > > work around the problem, but it's probably not very safe. > > Thanks for support. > > I updated the kernel on another PC from yesterday's source (cvsup-ed > about Jun 19 14:00 JST) and, what a miracle, "mount_ntfs" did not get > system panic. > > I'll try the latest kernel on the PC on which I found this problem. I've committed a fix for this bug to CVS. Thanks for reporting it! Tim