From owner-freebsd-current@FreeBSD.ORG Thu Jun 19 08:36:11 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 61AD737B401 for ; Thu, 19 Jun 2003 08:36:11 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE86943F93 for ; Thu, 19 Jun 2003 08:36:10 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from dilbert.robbins.dropbear.id.au (210.50.220.6) by smtp01.syd.iprimus.net.au (7.0.015) id 3EED7FDA001B8394; Fri, 20 Jun 2003 01:36:05 +1000 Received: by dilbert.robbins.dropbear.id.au (Postfix, from userid 1000) id 81DE0C91F; Fri, 20 Jun 2003 01:35:58 +1000 (EST) Date: Fri, 20 Jun 2003 01:35:58 +1000 From: Tim Robbins To: NAKAJI Hiroyuki Message-ID: <20030620013558.A52145@dilbert.robbins.dropbear.id.au> References: <8665n4j3v0.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: <8665n4j3v0.fsf@xa12.heimat.gr.jp>; from nakaji@tutrp.tut.ac.jp on Tue, Jun 17, 2003 at 09:16:51PM +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: Thu, 19 Jun 2003 15:36:11 -0000 On Tue, Jun 17, 2003 at 09:16:51PM +0900, NAKAJI Hiroyuki wrote: > I updated my laptop kernel to 5.1-CURRENT and got into trouble. > > FreeBSD mebius 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Jun 17 09:36:21 JST 2003 root@mebius:/usr/obj/usr/src/sys/GENERIC i386 > > This laptop also runs Windows 2000 whose filesystem is NTFS and this > NTFS part is mounted from FreeBSD with read-only. > > /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. Tim