Details
-
Bug
-
Resolution: Fixed
-
Major
-
Lustre 2.11.0
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/740cdf26-c31d-11e7-88ab-52540065bddc.
The sub-test test_56xb failed with the following error:
hard links individually migrated (12 != 11)
strongly suspect this is due to the very recently landed "LU-6051 utils: allow lfs_migrate to handle hard links"
test 56xb is brand new, only introduced in this patch.
I'm wondering if this test has ever been passed on any SLES version.
Info required for matching: sanity 56xb
Attachments
Activity
more seen on b2_10:
https://testing.hpdd.intel.com/test_sets/62af78a4-2fa8-11e8-b3c6-52540065bddc
https://testing.hpdd.intel.com/test_sets/9ff156a6-2fa8-11e8-b3c6-52540065bddc
https://testing.hpdd.intel.com/test_sets/62af78a4-2fa8-11e8-b3c6-52540065bddc
https://testing.hpdd.intel.com/test_sets/f0f35630-2fda-11e8-b3c6-52540065bddc
https://testing.hpdd.intel.com/test_sets/f58874a0-306b-11e8-b74b-52540065bddc
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30616/
Subject: LU-10199 tests: Re-enable sanity test 56xb
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: d90d9cd45e977d1672272786cb74d4941b6604a2
The patch to re-enable this test was not landed, and it is still being skipped.
Steve Guminski (stephenx.guminski@intel.com) uploaded a new patch: https://review.whamcloud.com/30616
Subject: LU-10199 tests: Re-enable sanity test 56xb
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 14c03c1e43f62fa79fc38288834ebc0a5df40cf2
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30078/
Subject: LU-10199 utils: strip // from fid2path
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 116b73d69bf2462fa9e9b8b9f629794bbda90ee5
Ben Evans (bevans@cray.com) uploaded a new patch: https://review.whamcloud.com/30078
Subject: LU-10199 utils: strip // from fid2path
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 5a87fb56b121fdcd623cb9298e53903ee5719ff1
It would be good to have some examples of how this is broken, since I can't imagine how "lfs fid2path" is generating a non-absolute pathnames.
Steve Guminski (stephenx.guminski@intel.com) uploaded a new patch: https://review.whamcloud.com/30013
Subject: LU-10199 lfs: Fix file name comparison in lfs_migrate
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 3a7fd98d46729b0d430b6fe30c55cba275574303
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/29954/
Subject: LU-10199 utils: disable sanity test 56xb
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 3ac484707aecb97ab8aa4716110205108b0535ea
This problem is not fixed, only the test is in ALWAYS_EXCEPT on master.
As a general rule, any ticket with the always_except label should not be closed. This label should be removed when the patch that re-enables the test is landed. I've often found, as in this case, that a ticket is marked resolved, but the reason the test is no longer failing is because the test has been disabled.