Subject: kern/612: Chikago disk may confuse dosfs
To: None <email@example.com>
From: None <firstname.lastname@example.org>
Date: 12/05/1994 10:05:05
>Synopsis: a chikago disk mounted as dosfs can deadlock the kernel
>Responsible: gnats-admin (Kernel Bug People)
>Arrival-Date: Mon Dec 5 10:05:03 1994
>Originator: Martin Husemann
System: NetBSD euterpe.owl.de 1.0 NetBSD 1.0 (EUTERPE) #0: Wed Nov 16 13:08:17 MET 1994 email@example.com:/usr/src/sys/arch/i386/compile/EUTERPE i386
Also tested (same effect) on a current kernel from yesterday's sup.
I accidently inserted a 1.44MB Chikago disk and mounted it with "-t dosfs".
After some work (including rm -rf of a subtree on the disk that contains
directories and files with long names, which failed, of course) I copied a
600 kB file to the disk. This never finished and I couldn't log in on other
term's (I could type the login name and ENTER, but then nothing would happen).
Microsoft claims it's new filesystem internals are compatible (and
transparent) to low-level utilities which are not aware of Chikago changes
if they don't play fsck-games.
I'll investigate further, I'm not sure yet.
None known (yet).
Maybe the chikago file system changes should be integrated
Can anybody point me to papers describing the new dosfs'
internal structure? I only found a white paper describing
the changes from the user level (long names are aliased similar
to Sun's PC-NFS).