From owner-freebsd-current@FreeBSD.ORG Fri Jun 20 07:42:05 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 A5DED37B401 for ; Fri, 20 Jun 2003 07:42:05 -0700 (PDT) Received: from pcat.heimat.gr.jp (catv-129-243.tees.ne.jp [202.216.129.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0162343FD7 for ; Fri, 20 Jun 2003 07:42:04 -0700 (PDT) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [202.216.136.35]) by pcat.heimat.gr.jp (8.12.9/8.12.9) with ESMTP id h5KEfxgm094440 for ; Fri, 20 Jun 2003 23:41:59 +0900 (JST) (envelope-from nakaji@tutrp.tut.ac.jp) Sender: nakaji@xa12.heimat.gr.jp To: freebsd-current@freebsd.org References: <8665n4j3v0.fsf@xa12.heimat.gr.jp> <8665n4j3v0.fsf@xa12.heimat.gr.jp> <20030620013558.A52145@dilbert.robbins.dropbear.id.au> From: NAKAJI Hiroyuki MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Fri, 20 Jun 2003 23:41:57 +0900 In-Reply-To: <20030620013558.A52145@dilbert.robbins.dropbear.id.au> (Tim Robbins's message of "Fri, 20 Jun 2003 01:35:58 +1000") Message-ID: <86he6k4xqi.fsf@xa12.heimat.gr.jp> User-Agent: T-gnus/6.16.2 (based on Gnus v5.10.2) (revision 01) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.4 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.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: Fri, 20 Jun 2003 14:42:05 -0000 >>>>> 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. -- NAKAJI Hiroyuki