https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-3613 Lustre <p>Getting all parent fid + name of an entry currently requires several calls with the current api, and is a big waste of RPCs:<br/> To get all path for an entry, we need to call fid2path,<br/> so this needs to call path2fid first, as fid2path requires a fid argument.<br/> Then, we need to call path2fid again for each path returned by fid2path.</p> <p>It would be much simpler to provide a wrapper that would directly read and decode link ea information.<br/> This would return all parent_fid+name for a given path.<br/> (this would also implements a fid -&gt; parent_fid+name interface,<br/> by passing a path in .lustre/fid).</p> <p>I'll submit a patch to be (hopefully) included in 2.5.</p> LU-3613

Get parent_fid + name for an entry

Improvement Minor Resolved Fixed Jinshan Xiong Thomas LEIBOVICI - CEA liblustreapi patch Mon, 22 Jul 2013 12:33:13 +0000 Fri, 31 Oct 2014 23:16:47 +0000 Fri, 31 Oct 2014 17:15:44 +0000 Lustre 2.5.0 Lustre 2.7.0 0 7 <p>pushed as change: <a href="http://review.whamcloud.com/7069" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7069</a></p> <p>The change has Jenkins and Maloo green lights - if you can take a look at it. Thanks.</p> <p>Since 2.6.0, definitions of link_ea* structures is no longer part of installed headers accessible for client applications (previously in lustre_idl.h).<br/> This is definitely cleaner, but now there is no possible workaround to decode linkea directly as a client application.<br/> So this patch (<a href="http://review.whamcloud.com/7069" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/7069</a>) becomes a requirement to get parent FID for an entry in Lustre 2.6.</p> <p>Landed for 2.7</p> <p>There'll be a follow-up patch to implement improvements the reviewers suggested on gerrit. Shall I open a new ticket for that?</p> <p>I think that would be best. We can link the new ticket to this one</p> <p>To track the follow-up patch.</p> Related LU-5837 LU-5613 Development Rank 1|hzvvsf: Rank (Obsolete) 9289