Date: Fri, 02 May 2008 16:40:23 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Bruce Evans <brde@optusnet.com.au> Cc: freebsd-bugs@freebsd.org, gavin@freebsd.org, bug-followup@freebsd.org Subject: Re: kern/122961: write operation on msdosfs file system causes panic Message-ID: <481B27D7.4020701@bsdforen.de> In-Reply-To: <20080503002252.L98216@delplex.bde.org> 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> <481AD71C.7030100@bsdforen.de> <20080503002252.L98216@delplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > On Fri, 2 May 2008, Dominic Fandrey wrote: > >> 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. > > Now we have a better argument for not axing non-port ntfs :-). I think > it sort of works read-only. Too bad we're no closer to understand the > msdosfs problem. > > Bruce It was really all my fault, I forgot to rebuild fusefs-kmod after updating my kernel. I'm sorry (not really) that I cannot serve you helpful data for the msdosfs problems other people have expressed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?481B27D7.4020701>