[LU-5731] sanity-lfsck test_18a: Created: 13/Oct/14 Updated: 13/Feb/16 Resolved: 23/Nov/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | Lustre 2.7.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Maloo | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | HB | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 16091 | ||||
| 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_18a failed with the following error: (6.1) Expect 1 fixed on mds1, but got: 2 Please provide additional information about the failure here. Info required for matching: sanity-lfsck 18a |
| Comments |
| Comment by nasf (Inactive) [ 21/Oct/14 ] |
|
sanity-lfsck test_18a assume that before the test start, there were no orphan OST-objects in the system. It is the test_18a itself to generate orphan OST-object during the test. Unfortunately, there were some orphan OST-object left from other former tests. So more orphan OST-objects have been found and repaired by test_18a. What we need to do is NOT to adjust the test scripts, but found out why there are orphan OST-objects before the test_18a. After some investigation, I found that in sanity test_14, the async updates for LFSCK have not been handled completely when the LFSCK finished, although before the LFSCK exit, it called dt_sync(), but current dt_sync() ignores the async updates that are handled by background ptlrpcd threads directly. Then those async LFSCK updates generated some orphan OST-objects, and made the test environment dirty. |
| Comment by nasf (Inactive) [ 21/Oct/14 ] |
|
Here is the patch: |
| Comment by Jian Yu [ 23/Oct/14 ] |
|
One more instance on master branch: https://testing.hpdd.intel.com/test_sets/71f79e8a-59e7-11e4-aa32-5254006e85c2 |
| Comment by Gerrit Updater [ 23/Nov/14 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/12359/ |