Edward Shishkin <edward@xxxxxxxxxx> wrote: > 1) What is the number of the failed step? Here is the log. The fact it happens after umount/remount suggests the metadata used changed a bit: Running tests in file ./tests/encryption/crypt.t [23:52:46] ./tests/encryption/crypt.t .. ========================= TEST 1 (line 8): glusterd [23:52:46] ./tests/encryption/crypt.t .. 1/? RESULT 1: 0 ========================= TEST 2 (line 9): pidof glusterd RESULT 2: 0 ========================= TEST 3 (line 12): gluster --mode=script --wignore volume create patchy bacasable.example.net:/d/backends/patchy1 [23:52:46] ./tests/encryption/crypt.t .. 3/? RESULT 3: 0 ========================= TEST 4 (line 13): patchy volinfo_field patchy Volume Name RESULT 4: 0 ========================= TEST 5 (line 14): Created volinfo_field patchy Status RESULT 5: 0 ========================= TEST 6 (line 15): 1 brick_count patchy [23:52:46] ./tests/encryption/crypt.t .. 6/? RESULT 6: 0 ========================= TEST 7 (line 19): gluster --mode=script --wignore volume set patchy performance.quick-read off RESULT 7: 0 ========================= TEST 8 (line 20): off volinfo_field patchy performance.quick-read [23:52:46] ./tests/encryption/crypt.t .. 8/? RESULT 8: 0 ========================= TEST 9 (line 21): gluster --mode=script --wignore volume set patchy performance.write-behind off RESULT 9: 0 ========================= TEST 10 (line 22): off volinfo_field patchy performance.write-behind [23:52:46] ./tests/encryption/crypt.t .. 10/? RESULT 10: 0 ========================= TEST 11 (line 23): gluster --mode=script --wignore volume set patchy performance.open-behind off RESULT 11: 0 ========================= TEST 12 (line 24): off volinfo_field patchy performance.open-behind RESULT 12: 0 ========================= TEST 13 (line 27): gluster --mode=script --wignore volume set patchy encryption on [23:52:46] ./tests/encryption/crypt.t .. 13/? RESULT 13: 0 ========================= TEST 14 (line 28): on volinfo_field patchy features.encryption RESULT 14: 0 ========================= TEST 15 (line 31): gluster --mode=script --wignore volume set patchy encryption.master-key /tmp/patchy-master-key [23:52:46] ./tests/encryption/crypt.t .. 15/? RESULT 15: 0 ========================= TEST 16 (line 38): gluster --mode=script --wignore volume start patchy [23:52:46] ./tests/encryption/crypt.t .. 16/? RESULT 16: 0 ========================= TEST 17 (line 39): Started volinfo_field patchy Status RESULT 17: 0 ========================= TEST 18 (line 42): glusterfs --attribute-timeout=0 --entry-timeout=0 --volfile-server=bacasable.example.net --volfile-id=patchy /mnt/glusterfs/0 RESULT 18: 0 ========================= TEST 19 (line 48): ./tests/encryption/frag /mnt/glusterfs/0/testfile /tmp/patchy-goodfile 262144 500 [23:52:46] ./tests/encryption/crypt.t .. 19/? RESULT 19: 0 ========================= TEST 20 (line 52): ln /mnt/glusterfs/0/testfile /mnt/glusterfs/0/testfile-link RESULT 20: 0 ========================= TEST 21 (line 53): mv /mnt/glusterfs/0/testfile /mnt/glusterfs/0/testfile-renamed RESULT 21: 0 ========================= TEST 22 (line 54): ln -s /mnt/glusterfs/0/testfile-link /mnt/glusterfs/0/testfile-symlink RESULT 22: 0 ========================= TEST 23 (line 55): rm -f /mnt/glusterfs/0/testfile-renamed RESULT 23: 0 ========================= TEST 24 (line 58): Y force_umount /mnt/glusterfs/0 RESULT 24: 0 ========================= TEST 25 (line 59): glusterfs --volfile-server=bacasable.example.net --volfile-id=patchy /mnt/glusterfs/0 RESULT 25: 0 ========================= TEST 26 (line 61): diff -u /mnt/glusterfs/0/testfile-symlink /tmp/patchy-goodfile diff: /mnt/glusterfs/0/testfile-symlink: Invalid argument not ok 26 RESULT 26: 2 > 2) What endianess does your machine have? Little endian (i386) -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@xxxxxxxxxx _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
