https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-5004 Lustre <p>This issue was created by maloo for wangdi &lt;di.wang@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/84d88c86-d313-11e3-8c68-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/84d88c86-d313-11e3-8c68-52540035b04c</a>.</p> <p>The sub-test test_77b failed with the following error:</p> <blockquote> <p>file compare failed</p> <p>error: set_param: setting /proc/fs/lustre/osc/lustre-OST0000-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0001-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0002-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0003-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0004-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0005-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> error: set_param: setting /proc/fs/lustre/osc/lustre-OST0006-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument<br/> set checksum type to crc32<br/> fail_loc=0x80000408<br/> /tmp/f77-temp /mnt/lustre/f77b.sanity differ: byte 1, line 1<br/> sanity test_77b: @@@@@@ FAIL: file compare failed </p></blockquote> <p>Info required for matching: sanity 77b</p> LU-5004

Test failure on test suite sanity, subtest test_77b file compare failed

Bug Minor Resolved Cannot Reproduce WC Triage Maloo Sat, 3 May 2014 23:04:05 +0000 Thu, 9 Jan 2020 07:31:12 +0000 Thu, 9 Jan 2020 07:31:12 +0000 0 2 <p>Is this test failing for other patches? It seems strange that tests would suddenly start failing in this manner. One other possibility is that this failure is related to a specific test node (e.g. AMD CPUs) that does not have crc32 hardware support. </p> <p>Close old bug</p> Development Rank 1|hzwlrr: Rank (Obsolete) 13853 Severity