Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.9.0
-
None
-
3
-
14946
Description
This issue was created by maloo for John Hammond <john.hammond@intel.com>
This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/307abe62-0cd8-11e4-8ce3-5254006e85c2.
The sub-test test_77i failed with the following error:
algo set to crc32 instead of adler
Info required for matching: sanity 77i
Attachments
Issue Links
Activity
One more failure instance on master branch:
https://testing.hpdd.intel.com/test_sets/a136d632-b36a-11e6-a0b8-5254006e85c2
Ashish Purkar (ashish.purkar@seagate.com) uploaded a new patch: http://review.whamcloud.com/23644
Subject: LU-5361 tests: Incorrect checksum algorithm reported
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: a476729a9ca737bd00d611c870837d2b7977317c
The algorithm used depends on the CPU hardware support. It may be that CRC32 is a lot faster than Adler, so Adler is not available. That probably needs a fix to the test.
Another failure on master at https://testing.hpdd.intel.com/test_sets/1654529c-7e46-11e5-965a-5254006e85c2
2015-11-13 21:15:03 - https://testing.hpdd.intel.com/test_sets/aae313cc-8a66-11e5-ba42-5254006e85c2
2016-01-21 15:34:52 - https://testing.hpdd.intel.com/test_sets/70bbba40-c06d-11e5-acc7-5254006e85c2
2016-01-21 23:10:38 - https://testing.hpdd.intel.com/test_sets/cb1f99b2-c0ad-11e5-b0fe-5254006e85c2
2016-02-01 15:26:49 - https://testing.hpdd.intel.com/test_sets/11b856f0-c911-11e5-bedf-5254006e85c2
2016-02-08 08:55:14 - https://testing.hpdd.intel.com/test_sets/2c566f30-ce8c-11e5-af15-5254006e85c2
2016-02-08 16:43:35 - https://testing.hpdd.intel.com/test_sets/2a62fb4c-ce9d-11e5-bfa1-5254006e85c2
+1 again on master : https://testing.hpdd.intel.com/test_sets/aa999490-764d-11e5-86b7-5254006e85c2
Another failure instance on master:
https://testing.hpdd.intel.com/test_sets/269d217c-738a-11e5-ae2e-5254006e85c2
Another instance of this error:
2015-07-16 03:17:56 - https://testing.hpdd.intel.com/test_sets/156e74ae-2b83-11e5-b0b2-5254006e85c2
2015-07-20 15:59:05 - https://testing.hpdd.intel.com/test_sets/03de714c-2f13-11e5-bc70-5254006e85c2
2015-08-21 10:53:05 - https://testing.hpdd.intel.com/test_sets/7461086c-483b-11e5-813b-5254006e85c2
Note also that this test failure appears to have been around a long time and is unlikely to be (directly) related to the checksum algorithm changes. LU-3243 predates it, and was closed when the debug patch was landed, even though the comment said:
I submitted http://review.whamcloud.com/6205 to improve the error message, but that is not fixing the bug here.
I also see several cases of this test failing if there is an error reading from /proc, but I think those predate the 6205 patch, which prints out the actual checksum algorithm used and doesn't just fail if '[adler]' is not found.
When fixing this, the test_77i() code could be cleaned up a bit. It uses cut -d= when it could be using lctl get_param -N to just print the parameter names. It should also use $(...) for subshells instead of `...`, and it should print out the OSC device on which the failure(s) happened.
Actually, the whole check could be simplified to:
lctl get_param osc.*osc-[^mM]*.checksum_type | grep -v '\[adler\]' && error "checksum algorithm not set to adler"
Abrarahmed Momin (kais_abrar@yahoo.co.in) uploaded a new patch: https://review.whamcloud.com/25745
Subject:
LU-5361llite: Remove OBD_FAIL_OSC_CONNECT_CKSUMProject: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: b3e0a5be1edf02b8facb8928b746c23e17a376c3