Subject: kern/4033: i386 msdosfs support appears to be unstable/broken
To: None <email@example.com>
From: Ken Wellsch <firstname.lastname@example.org>
Date: 08/24/1997 14:49:41
>Synopsis: i386 msdosfs support appears to be unstable/broken
>Responsible: kern-bug-people (Kernel Bug People)
>Arrival-Date: Sun Aug 24 11:50:02 1997
>Originator: Ken Wellsch
>Release: NetBSD-current and 081597 i386 snapshot
Gateway P5-166, NetBSD-1.2G
System: NetBSD link 1.2G NetBSD 1.2G (LINK) #0: Sun Aug 3 12:00:43 EDT 1997 kwellsch@link:/usr/src/sys/arch/i386/compile/LINK i386
In order to do some CD-R mastering, I have been using NetBSD
to write a directory tree onto a JAZ drive with an MS-DOS
file-system using an Adaptec 2940 controller. I'm stuck
using Windows/95 commercial software for the actual burning.
I upgraded the system in question to the 081597 snapshot from
a copy of NetBSD-current of several months ago. I also tried
NetBSD-current as of Aug 23/1997 (tar_files).
I rdist my directory tree (e.g. 50Mb) from one system onto
the "mount_msdos -l" mounted file system on the system in
question - which after a fair mount of disk activity, begins
to slow, then the machine freezes/hangs. I normally run
xdm on that system but just once when I'd killed xdm in case
memory (16Mb) limitations were involved, I got a kernel panic
that dropped me into db>.
I also tried copying some large .tgz files onto said
file-system. I then did some renaming via "mv" - things
got really weird. File names got messed up then blamo I
had a bad msdos file system.
Resort to using Windows/95 directly and live with silly
file renaming that occurs... sigh.