nasty VFAT incident in 2.1.65

Kevin Moule (krmoule@undergrad.math.uwaterloo.ca)
Wed, 3 Dec 1997 13:06:28 -0500


Hi,

This has got to be the first time linux has ever done anything
unsatisfactory in all the years i've been using it. But I guess
its got to happen sometime but anyway. This is what i did:

(my FAT32 /dev/hda1 is mounted on /mnt as vfat)

/mnt/quake/> mv Fortress fortress

It complained about moving 'fortress' into 'fortress/fortess' or something
similiar. So i tried this:

/mnt/quake/> mv Fortress f
/mnt/quake/> mv f fortress

And afterwards i did a 'ls -la' to see what happened and neither my
Fortress, fortress or f directory was there. Just up and disappeared.
So i decided to unmount the drive. Reboot into win95 to see if it
maybe is still there or can be fixed or something. When unmounting
the drive i get this:

VFS: Busing inodes in unmount. Self-destruct in 5 seconds. Bye-bye...

Well i didn't self destruct, but i wasn't too happy. Once in Win95 the
directory wasn't there either and scandisk produced 20megs in lost
fragments.

Anyone got an explanation of why this happened?

Kevin
-