[LU-5080] Test failure on test suite sanity-lfsck, subtest test_11b Created: 19/May/14 Updated: 01/Mar/19 Resolved: 01/Mar/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | Lai Siyao |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | dne | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 14016 | ||||||||
| Description |
|
This issue was created by maloo for Nathaniel Clark <nathaniel.l.clark@intel.com> This issue relates to the following test suite run: The sub-test test_11b failed with the following error:
Info required for matching: sanity-lfsck 11b This seems to be always followed by failure in sanity-lfsck/12 ( |
| Comments |
| Comment by Andreas Dilger [ 21/May/14 ] |
|
It looks like the test itself is defective, since it is expecting the OST objects to be assigned in the 0x100000000 range (IDIF FID), but in fact the OST has been assigned FID SEQ 0x200000400 in DNE FID-on-OST mode, as can be seen in the OST console log: 04:51:36:Lustre: lustre-OST0000: deleting orphan objects from 0x200000400:34 to 0x200000400:65 04:51:36:Lustre: lustre-OST0000: deleting orphan objects from 0x200000401:34 to 0x200000401:65 04:51:36:Lustre: lustre-OST0000: deleting orphan objects from 0x200000402:34 to 0x200000402:65 Probably what needs to happen is the test should check the last_id file before corrupting it, and then verify it has the same sequence afterward, instead of hard-coding 0x10000000. |
| Comment by James Nunez (Inactive) [ 29/Jul/15 ] |
|
Looks like we are experiencing this issue in review-dne-part-2: |
| Comment by Andreas Dilger [ 01/Mar/19 ] |
|
Pushing a patch via |