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-13527 Lustre <p>It would be useful to allow reverse pathname lookup of OST FIDs via "<tt>lfs fid2path /mntpt &lt;fid&gt;</tt>", since the OST FIDs are sometimes referenced in console error messages, and it is useful to be able to do a pathname lookup without first having to manually run e.g. "<tt>debugfs -c -R 'stat &lt;O/&lt;f_seq&gt;/d$((&lt;f_oid&gt; %32))/&lt;f_oid&gt;' /dev/&lt;ostdev&gt;</tt>" or "<tt>ll_decode_filter_fid</tt>" on the underlying OST.</p> <p>The client would need to first determine that this is an OST FID from the FLDB, then fetch the "<tt>fid</tt>" xattr that contains the MDT parent FID from the OST object (if it exists), and then do the normal <tt>fid2path</tt> lookup on the returned MDT parent FID.</p> LU-13527

allow OST FID lookup via lfs fid2path

Improvement Major Open Unresolved WC Triage Andreas Dilger medium Thu, 7 May 2020 00:10:13 +0000 Wed, 10 Jan 2024 22:18:45 +0000 0 4 <p>It should be possible to make a decision in <tt>__ll_fid2path()</tt> whether to call <tt>OBD_IOC_FID2PATH</tt> on the LMV/MDC export or the LOV/OSC export based on the FID being requested. There would need to be handling of <tt>OBD_IOC_FID2PATH</tt> in <tt>lov_iocontrol()</tt> and <tt>osc_iocontrol()</tt> and then something similar to <tt>mdc_ioc_fid2path()</tt> to call <tt>obd_get_info(KEY_FID2PATH)</tt> to send the RPC to the OST.</p> <p>On the OST side, handling of <tt>KEY_FID2PATH</tt> would be needed in <tt>ofd_get_info_hdl()</tt> to extract the MDT FID from the OST object and return it in back to the client. While it isn't strictly required (there will not be any pathname returned), it makes sense to use <tt>struct getinfo_fid2path</tt> for the OST RPC so that it is handled consistently with the MDT RPC.</p> <p>Then the client can extract the MDT FID from the OST reply and execute the rest of the <tt>__ll_fid2path()</tt> operation as it does today.</p> Related LU-11638 LU-13124 Development Rank 1|i00zon: Rank (Obsolete) 9223372036854775807