Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 [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 https://jira.whamcloud.com/browse/LU-5985 Lustre <p>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".</p> <p>The LFSCK should guarantee that related inconsistency can be detected and repaired in spite of whether DEN has handled such case successfully or not.</p> 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 Bug Major Resolved Duplicate nasf nasf Thu, 4 Dec 2014 23:45:12 +0000 Tue, 5 Dec 2017 05:50:28 +0000 Tue, 5 Dec 2017 05:50:28 +0000 Lustre 2.7.0 0 4 <p>Is this fixed by the <a href="http://review.whamcloud.com/16035" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16035</a> patch "<a href="https://jira.whamcloud.com/browse/LU-6895" title="sanity-lfsck test 4 hung: bad entry in directory: rec_len is smaller than minimal - inode=3925999616" class="issue-link" data-issue-key="LU-6895"><del>LU-6895</del></a> osd-ldiskfs: handle REMOTE_PARENT_DIR properly"?</p> <p>The patch <a href="http://review.whamcloud.com/16035" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/16035</a> 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.</p> <p>Has not occurred for a long time</p> <p>reopen to change resolution type</p> Related LU-4876 Development Rank 1|hzx1x3: Rank (Obsolete) 16702 Severity