On 04/01/2014 08:01 PM, Mikulas Patocka wrote: >> 1) mdadm -C -l 5 -n 3 -c 64 --assume-clean /dev/md0 /dev/sd[xyz] >> 2) run 2/dmcrypt-all-verify.sh > > I tried to run "./dmcrypt-all-verify.sh --dev /dev/md0 --testdir > /mnt/test" and the result was this. > > That script is somehow buggy because it attempts to copy files that I have > in /usr/src to the test filesystem. It fills up the test filesystem and > fails. I don't know why is it trying to copy files not related to the test. Hi Mikulas, if it is the test I wrote years ago, it was in principle a hack, I need some filesystem with a lot files of different sizes. So I simply packed /usr and checked hash of all files before and after unpacking to test dmcrypt device. IMHO there should be some prepared archive which is just unpacked, not that it uses live /usr. (Obviously it need large enough device :-) But anyway, despite it is quite stupid test, it already proved to be very useful (I remember it discovered bugs in various patches several times). A IIRC it used several fs types and several encryption types (including null encryption which removes crypto layer influence, testing pure dmcrypt bio handling). Milan -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
