[LU-5985] LFSCK 5: remove dummy name entry from /REMOTE_PARENT_DIR if the MDT-object and its name entry reside on the same MDT Created: 04/Dec/14 Updated: 05/Dec/17 Resolved: 05/Dec/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.7.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 16702 | ||||||||
| Description |
|
This can happen when migrate directory MDT-object_A's metadata from MDT_x to MDT_y: all object_A's children name entries needs to be moved to MDT_y. If some name entry originally referenced a remote MDT-object_B which was linked under "/REMOTE_PARENT_DIR" with a dummy name entry on MDT_y, but after the migration, the MDT-object_B and its new name entry resides on the same MDT_y, then the dummy entry for the MDT-object_B should be removed from "/REMOTE_PARENT_DIR". The LFSCK should guarantee that related inconsistency can be detected and repaired in spite of whether DEN has handled such case successfully or not. |
| Comments |
| Comment by Andreas Dilger [ 24/Aug/15 ] |
|
Is this fixed by the http://review.whamcloud.com/16035 patch " |
| Comment by nasf (Inactive) [ 25/Aug/15 ] |
|
The patch http://review.whamcloud.com/16035 does not related with this issue. Generally, the migration logic will handle that. The namespace LFSCK only needs to handle the case of migration failure (partly done): the name entry has been added to the new parent directly, but the old ".." has not been updated. |
| Comment by Peter Jones [ 31/Aug/15 ] |
|
Has not occurred for a long time |
| Comment by Andreas Dilger [ 05/Dec/17 ] |
|
reopen to change resolution type |