From owner-freebsd-bugs@FreeBSD.ORG Fri May 2 08:56:35 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38C91106566B; Fri, 2 May 2008 08:56:35 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id E8EB88FC0C; Fri, 2 May 2008 08:56:34 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.178.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id B9A4B8A013E; Fri, 2 May 2008 10:56:15 +0200 (CEST) Message-ID: <481AD71C.7030100@bsdforen.de> Date: Fri, 02 May 2008 10:55:56 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.12 (X11/20080422) MIME-Version: 1.0 To: Bruce Evans References: <200804211445.m3LEjNh6018941@freefall.freebsd.org> <480CC6F4.1000200@bsdforen.de> <20080422084732.H63563@delplex.bde.org> <480E1F9E.5070308@bsdforen.de> <20080423110846.I67125@delplex.bde.org> <480F9E0F.3010803@bsdforen.de> <20080424133415.G70715@delplex.bde.org> In-Reply-To: <20080424133415.G70715@delplex.bde.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org, gavin@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: kern/122961: write operation on msdosfs file system causes panic X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2008 08:56:35 -0000 Bruce Evans wrote: > On Wed, 23 Apr 2008, Dominic Fandrey wrote: > >> Bruce Evans wrote: >>> The broken nocluster* can be worked around by upgrading to a version of >>> mount_msdsosfs(8) that hasn't been broken by using nmount(2). >>> mount_msdsosfs(8) from RELENG_5 should work. >> >> I feel reluctant about downgrading to 5.x mount_msdosfs, > > But it would be an upgrage :-). Anyway, running mount_msdosfs on one > disposable file system that might panic should be safe. > >> however I can confirm that cp with large files does _not_ cause a >> panic. As far as I understand this confirms your theory. > > Not quite. I would have expected the problem to affect read() and write() > too unless the file system is mounted with -nocluster*. This can be closed. Your suggestions have been very helpful. It turned out that fusefs-ntfs is causing the panic, when I copy files from it.