[LU-8289] add ll_decode_linkea tool Created: 16/Jun/16  Updated: 20/Oct/16  Resolved: 20/Oct/16

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.9.0

Type: New Feature Priority: Minor
Reporter: Qian Yingjin (Inactive) Assignee: nasf (Inactive)
Resolution: Fixed Votes: 0
Labels: patch

Rank (Obsolete): 9223372036854775807

 Description   

A MDT recovered by fsck might contain some files under lost+found
directory of ldiskfs. And in order to get the right path to move
them to, the xattr of trusted.link could be used to extract the
parent FIDs.

This path adds an new tool ll_decode_linkea to dump the parent FIDs
of a file.



 Comments   
Comment by Qian Yingjin (Inactive) [ 16/Jun/16 ]

Li Xi (lixi@ddn.com) uploaded a new patch: http://review.whamcloud.com/#/c/20444/
Subject: LU-8289 utils: add ll_decode_linkea tool
Project: fs/lustre-release
Branch: master
Current Patch Set: 2
Commit: abbee94b12ff03e1dba985e44e31aa7e35f6b7a4

Comment by Peter Jones [ 16/Jun/16 ]

Fan Yong

Could you please review this work?

Thanks

Peter

Comment by nasf (Inactive) [ 17/Jun/16 ]

Some clarify: the namespace LFSCK (since Lustre-2.7) can recover the orphan MDT-object from the ldiskfs backend /lost+found back to its original client-visible namespace. So this tool is mainly used for old Lustre release or under the case that the customer does not wants to run namespace LFSCK that may take long time on very large system.

Comment by nasf (Inactive) [ 18/Jun/16 ]

Some enhancement can be considered: more integrated online tools that uses ll_decode_linkea and fid2path functionality, and can directly show the original position in the namespace; in further, it can move such orphan back to its original position.

Comment by Gerrit Updater [ 20/Oct/16 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/20444/
Subject: LU-8289 utils: add ll_decode_linkea tool
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 11a138cb9d005ef0180421bd17542071b63e18d9

Comment by Peter Jones [ 20/Oct/16 ]

Landed for 2.9

Generated at Sat Feb 10 02:16:15 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.