<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:37:47 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-3888] lfs getstripe should print FID</title>
                <link>https://jira.whamcloud.com/browse/LU-3888</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Given that lustre 2.x versions now support unique file identifier (FID) it would be rather useful to be able to specify that FID in lfs setstripe and lfs getstripe commands.&lt;/p&gt;

&lt;p&gt;Right now, if you have the single FID to a file, you can use lfs fid2path, however fid2path does not provide a full path to the file, so the parent FID is required. &lt;/p&gt;

&lt;p&gt;Once you have the parent FID and target FID you can use those to lookup the actual file path / name and then lfs setstripe / getstripe.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="20795">LU-3888</key>
            <summary>lfs getstripe should print FID</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="cfaber#1">Colin Faber [X]</reporter>
                        <labels>
                    </labels>
                <created>Thu, 5 Sep 2013 17:04:30 +0000</created>
                <updated>Thu, 29 Sep 2016 18:05:30 +0000</updated>
                            <resolved>Thu, 29 Sep 2016 18:05:30 +0000</resolved>
                                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="65956" author="adilger" created="Fri, 6 Sep 2013 16:17:05 +0000"  >&lt;p&gt;If you want to do operations by FID it should be possible to use /mnt/lustre/.lustre/fid/&lt;span class=&quot;error&quot;&gt;&amp;#91;fid_sequence:objid:ver&amp;#93;&lt;/span&gt; as the filename?  I haven&apos;t tried it, but it should work in theory. &lt;/p&gt;

&lt;p&gt;As for fid2path, this needs the mountpoint and then it can generate a full path. Without the mountpoint the FID is not unique. &lt;/p&gt;</comment>
                            <comment id="85011" author="adilger" created="Wed, 28 May 2014 07:44:30 +0000"  >&lt;p&gt;This patch doesn&apos;t implement getstripe for FIDs, but it does print the FID as part of &lt;tt&gt;lfs getstripe&lt;/tt&gt; output with the lmm_fid: label, which is a start:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/10465&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/10465&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I did verify that &lt;tt&gt;lfs getstripe -v /mnt/lustre/.lustre/fid/&lt;span class=&quot;error&quot;&gt;&amp;#91;fid_seq:fid_oid:0&amp;#93;&lt;/span&gt;&lt;/tt&gt; works properly.&lt;/p&gt;

&lt;p&gt;I&apos;m not sure what &lt;tt&gt;lfs setstripe&lt;/tt&gt; on a FID would do, since the file has to exist already, and this typically means it will already have a layout.&lt;/p&gt;</comment>
                            <comment id="127071" author="lokesh.jaliminche" created="Fri, 11 Sep 2015 12:47:23 +0000"  >&lt;p&gt;I have updated patch for getting FID info with -F option  and also added test case to check that. Regarding &quot;updating man page for -F option in lfs(1)&quot; is there any other procedure (like creating seperate ticket at LUDOC or something like that) ? because as far as  I know man page is not part of the lustre code.&lt;/p&gt;</comment>
                            <comment id="127177" author="adilger" created="Sat, 12 Sep 2015 21:02:57 +0000"  >&lt;p&gt;The man pages are in lustre/doc&lt;/p&gt;</comment>
                            <comment id="167739" author="gerrit" created="Thu, 29 Sep 2016 15:00:02 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/10465/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/10465/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-3888&quot; title=&quot;lfs getstripe should print FID&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-3888&quot;&gt;&lt;del&gt;LU-3888&lt;/del&gt;&lt;/a&gt; utils: print lmm_fid as part of getstripe&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 4dfa29e8e0e77add076ef992bb9061519669dc16&lt;/p&gt;</comment>
                            <comment id="167787" author="pjones" created="Thu, 29 Sep 2016 18:05:30 +0000"  >&lt;p&gt;Landed for 2.9&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzw0br:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10132</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>