Something may be broken in USB / usb-storage land.
I've got a 2GB USB stick here.
I want to copy it to an image file on my hard drive:
cat /dev/sdb > usbkey.image1
Make a second copy, with or without unplugging/replugging the stick:
cat /dev/sdb > usbkey.image2
After doing this, the two copies *differ*.
So I wrote a little program to compare them and determine *how* they differ,
and the result is very interesting.
Periodically, or or the other file has 8192 *zero* bytes inserted
in place of it's data. Not replacing it's data, just inserted
into the stream, causing the real data (which follows) to be offset by 8192.
If one skips over the inserted 8192 bytes in the file, the data from that point
onward matches the other file, until another 8192 zeros are encountered.
The total sizes of the two image files match each other,
but that's probably just due to the logic in the 'cat' program.
I wonder where those extraneous pairs of zero pages are coming from?
This makes USB drives somewhat unreliable for backups and the like,
which unfortunately is exactly what just about everybody uses them for.
This (so far) is with 2.6.23.1 (w/slab allocater), and 2.6.24-rc2,
on two different machines (both Intel based, but different chipset, CPU, RAM,
...).
I suspect not all brands/models of USB sticks would give the same results,
but it is rather worrisome that it happens at all.
Mmmmmm ????
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
