From owner-freebsd-bugs@FreeBSD.ORG Wed Apr 23 20:37:55 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 E7ABD1065674; Wed, 23 Apr 2008 20:37:55 +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 8A3B38FC1C; Wed, 23 Apr 2008 20:37:55 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.117.38.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id B8A418A083C; Wed, 23 Apr 2008 22:37:47 +0200 (CEST) Message-ID: <480F9E0F.3010803@bsdforen.de> Date: Wed, 23 Apr 2008 22:37:35 +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> In-Reply-To: <20080423110846.I67125@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: Wed, 23 Apr 2008 20:37:56 -0000 Bruce Evans wrote: > On Tue, 22 Apr 2008, Dominic Fandrey wrote: > >> Bruce Evans wrote: >>> On Mon, 21 Apr 2008, Dominic Fandrey wrote: >>> This seems to be a bug in usb (umass) or the particular usb drive... >>> ... >>> >>> To check that this is the bug, mount msdosfs with -o >>> noclusterr,noclusterw >>> under RELENG_7 or later (the bug also affects RELENG_6, but these mount >>> options are broken in RELENG_6). ... >> >> # mount -t msdosfs -o >> noatime,noexec,-L=en_GB.UTF-8,noclusterr,noclusterw /dev/da0 /mnt/tmp >> mount_msdosfs: /dev/da0: mount option is unknown: Invalid >> argument >> >> It seems they are also broken under RELENG_7 from the day before >> yesterday. > > Oops, it is indeed broken there too. msdosfs in RELENG_7 is in the state > that I thought RELENG_6 was in (missing critical MFCs only for nocluster* > in the options list and to fix panics related to the dirty flag), while > msdosfs in RELENG_6 is just too old to support clustering. > > 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, however I can confirm that cp with large files does _not_ cause a panic. As far as I understand this confirms your theory. How can I provide more useful information?