2.6.19: File system corruption "stuck" until device is replugged

[Andrey Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I had USB stick (fat32) that reported file system corruption on mount and 
hence was mounted read-only. No amount of umount/dosfsck/mount could make it 
rw again. dosfsck reported device as clean but it still would mount ro and I 
continued to see directory that had been deleted by the very first dosfsck 
run! I unplugged it, looked under Win2k - it was OK - and only then did I 
notice that directory claimed as corrupted did not even exist. Replugging 
it - mounted OK.

I am not sure if this is a bug or "work as designed". May be this is specific 
fat32 problem; still it does not look right?

TIA

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFi2YfR6LMutpd94wRAquCAKC3n8DjRGRqDYdfP6tNGvlg5sG0MQCfQRNJ
89HQuNaAWuLzJkkKayVrLks=
=m0rH
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/