On 18.09.2009, Milan Broz wrote: > Yes it was hardcoded to use sha1. But it is no longer true anyway. > Using another hash (all algorithms provided by libgcrypt) is already > implemented in devel code. As reported some weeks ago, the buffer i/o errors are still present with the latest svn code (from today): [....] Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 32 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 4 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 5 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 6 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 7 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 8 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 9 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 10 Sep 19 18:33:05 liesel kernel: Buffer I/O error on device dm-4, logical block 11 Sep 19 18:35:57 liesel kernel: __ratelimit: 37 callbacks suppressed Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 64 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 65 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 120 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 121 Sep 19 18:35:57 liesel kernel: Buffer I/O error on device dm-4, logical block 8 [....] cryptsetup-1.0.7 works fine. _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
