[LU-5767] LFSCK 3: replace LFSCK RPC with normal OUT RPC to create orphan parent on remote MDT Created: 18/Oct/14 Updated: 19/Jan/15 Resolved: 19/Jan/15 |
|
| 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: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | HB | ||
| Severity: | 3 |
| Rank (Obsolete): | 16188 |
| Description |
|
When the namespace LFSCK tries to repair the missing name entry, means inserting the lost name entry back to its parent directory, it may find that the parent MDT-object is also lost. Under such case, the namespace LFSCK will firstly create the missing parent MDT-object as an orphan and insert into the .lustre/lost+found/MDTxxxx/ directory with the name: ${FID}-P-${conflict_version}.
Then insert the lost name entry into the orphan parent according to the MDT-object's linkEA. Currently, the namespace LFSCK uses LFSCK RPC to handle the case of creating orphan parent MDT-object on remote MDT. It is not the normal way for cross-MDTs modification that usually will be handled via OUT RPC. Please refer to the comment on gerrit for more discussion: http://review.whamcloud.com/#/c/11391/28/lustre/lfsck/lfsck_namespace.c,cm |
| Comments |
| Comment by nasf (Inactive) [ 18/Oct/14 ] |
|
On concern: if we does not resolve the inconsistency related with the .lustre/lost+found/MDTxxxx at the LFSCK beginning, then how the layout LFSCK can handle the orphan OST-objects after that? The layout LFSCK can run independently with namespace LFSCK, but it can neither realise that the object for .lustre/lost+found/MDTxxxx may be orphan, nor repair such inconsistency. |
| Comment by Andreas Dilger [ 21/Oct/14 ] |
|
Alex, Fan Yong, is this supposed to be fixed for 2.7 or can it land in 2.8? It looks like it concerns the wire protocol. |
| Comment by nasf (Inactive) [ 22/Oct/14 ] |
|
I prefer to land it before Lustre-2.7 release. I will handle it as bug fixing after 2.7 feature frozen. |
| Comment by Gerrit Updater [ 23/Dec/14 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13172 |
| Comment by nasf (Inactive) [ 23/Dec/14 ] |
|
This patch should be landed to master before Lustre-2.7 release to avoid interoperability issues in future. |
| Comment by Gerrit Updater [ 19/Jan/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13172/ |
| Comment by Peter Jones [ 19/Jan/15 ] |
|
Landed for 2.7 |