What a strange coincidence that it affected git pack files in both cases.
It's almost too improbable...
Probably more than a coincidence I think, the question is what though...
Some SSD drives (or rather the cheap wear levelling controllers in things
like USB sticks) have firmware which tries to recognise certain data
structures of common filesystems (like FAT and NTFS), and uses information
in those data structures to optimise the allocation and erasure of blocks
(for example the free space linked list in FAT). If the data you were
saving to the disk was similar to one of those data structures, you might've
triggered one of those algorithms, which would cause data corruption. This
is common in high performance usb sticks because they want to pre-erase
blocks on file deletion for operating systems not supporting SCSI TRIM - I
imagine the same technology might carry across to cheap SSD's.
Not much BTRFS can do about it though. If the piece of data that triggers
the bug could be identified, workarounds could possibly be introduced for
the particular buggy controllers.
Oliver Mattos
(resent as I emailled wrong recipients before)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
