After some research it seems that this problem exists in some changes to libata in the 2.6.20 kernel, it seems that k9copy just happens to be the software tripping on the bug though it is not the root cause.
After some research it seems that this problem exists in some changes to libata in the 2.6.20 kernel, it seems that k9copy just happens to be the software tripping on the bug though it is not the root cause.