it looks like between 2.1.130 and 2.1.131 some new bug got into
the vfat code:
Whenever I load a file on a vfat partition with StarOffice, make
some changes and save it again, I get all kinds of mysterious
errors. StarOffice will either crash while saving the file, or
report something about "unknown format" when I try to load it
again - obviously because the file got written incorrectly. When
I unmount the file system, I always get an error message saying:
VFS: Busy inodes after unmount. Self-destruct in 5 seconds...
When I run scandisk under DOS afterwards, I find a bunch of file
fragments (which seem to contain the data that should have been
written to the original files).
I don't know what exactly goes wrong, but these problems
consistently occur with kernel 2.1.131. When I use an older
version (up to 2.1.130) things are O.K.
regards
Peter Daum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/