[LU-5004] Test failure on test suite sanity, subtest test_77b file compare failed Created: 03/May/14  Updated: 09/Jan/20  Resolved: 09/Jan/20

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 13853

 Description   

This issue was created by maloo for wangdi <di.wang@intel.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/84d88c86-d313-11e3-8c68-52540035b04c.

The sub-test test_77b failed with the following error:

file compare failed

error: set_param: setting /proc/fs/lustre/osc/lustre-OST0000-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0001-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0002-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0003-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0004-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0005-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
error: set_param: setting /proc/fs/lustre/osc/lustre-OST0006-osc-ffff88007a2e0400/checksum_type=crc32: Invalid argument
set checksum type to crc32
fail_loc=0x80000408
/tmp/f77-temp /mnt/lustre/f77b.sanity differ: byte 1, line 1
sanity test_77b: @@@@@@ FAIL: file compare failed

Info required for matching: sanity 77b



 Comments   
Comment by Andreas Dilger [ 05/May/14 ]

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.

Comment by Andreas Dilger [ 09/Jan/20 ]

Close old bug

Generated at Sat Feb 10 01:47:42 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.