--On onsdag, juli 29, 2009 09.07.16 -0400 Josh Kelley <joshkel@gmail.com> wrote:
On Wed, Jul 29, 2009 at 12:31 AM, Owen Townend<owen.townend@gmail.com> wrote:Just to be clear here: When using one of these fraudulent drives filling it up will produce no errors. Reading it back will show corruption once passed the actual size of the device. Your comment didn't mention whether you were able to successfully read back the data after it was written in Windows.Sorry I wasn't clearer. I filled it up (to within 1MB of its reported capacity) in Windows and then was able to read it back successfully both in Windows and Linux. Josh Kelley
Don't know if it is at all related, but I had some usb sticks
behaving quiet strange too (on a debian etch 64bit).
The symptons where that a file (kernel actually) that was copied
to the stick could not be run the next time the stick was mounted.
Now the nasty part was that if I used e.g. tar or dd to put the
file on stick instead of cp the file _was_ correct after a remount.
I also noticed that it took signicifantly longer to use tar than
cp (though perhaps tar is writing chars instead of blocks which
could explain that?).
I never found out what was causing the behaviour, so please share
any findings to your problem.
Regards,
Emil