<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:03:02 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-28] Ability for client to mount subdirectories of a Lustre filesystem</title>
                <link>https://jira.whamcloud.com/browse/LU-28</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In kicking around some ideas for the use of Lustre as a replacement for NFS user directories (home and application areas), the thought of being able to export/mount a subdirectory of a Lustre LOV came up.&lt;/p&gt;</description>
                <environment></environment>
        <key id="10137">LU-28</key>
            <summary>Ability for client to mount subdirectories of a Lustre filesystem</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</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="wangshilong">Wang Shilong</assignee>
                                    <reporter username="laisiyao">Lai Siyao</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Mon, 20 Dec 2010 17:50:17 +0000</created>
                <updated>Fri, 23 Sep 2016 13:05:16 +0000</updated>
                            <resolved>Mon, 18 Apr 2016 12:55:49 +0000</resolved>
                                    <version>Lustre 2.0.0</version>
                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due>Fri, 28 Jan 2011 00:00:00 +0000</due>
                            <votes>0</votes>
                                    <watches>19</watches>
                                                                            <comments>
                            <comment id="10370" author="laisiyao" created="Thu, 30 Dec 2010 05:05:14 +0000"  >&lt;p&gt;Basically there are two ways to implement this:&lt;br/&gt;
1. client lookup the filesystem root, and then walk the filesystem (based on the&lt;br/&gt;
   subdirectory path) and instantiate the subdirectory as the mountpoint root.&lt;br/&gt;
   This can be implemented entirely on the client and does not require any protocol&lt;br/&gt;
   changes.&lt;br/&gt;
2. change the MDS_GETSTATUS RPC to pass the subdirectory pathname from the client&lt;br/&gt;
   to the MDS, and have it do the pathname traversal locally and return the &quot;root&quot;&lt;br/&gt;
   FID for the subdirectory. This needs protocol changes, though simple ones that&lt;br/&gt;
   can be implemented in a backward-complatible manner.&lt;/p&gt;

&lt;p&gt;The advantage of the first way is:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;no protocol changes.&lt;/li&gt;
	&lt;li&gt;client changes only, no compatibility issue.&lt;/li&gt;
	&lt;li&gt;pathname transversal is more convenient and natural in client, especially for CMD&lt;br/&gt;
  which may involve several MDS.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Due to the above advantages this feature will be implemented in the first way.&lt;/p&gt;

&lt;p&gt;However there are some limitations:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&amp;lt;mountpoint&amp;gt;/.lustre doesn&apos;t exist for subdirectory mount. This &apos;.lustre&apos; directory&lt;br/&gt;
  is maintained under root directory on MDS for whole filesystem. Though we may create&lt;br/&gt;
  a link under subdirectory pointing to it, it may leak fids outside of its namespace.&lt;br/&gt;
  Currently the only affected utility is lustre_rsync, but user can do a normal mount&lt;br/&gt;
  and apply there (actually lustre_rsync should work on a normal mount, otherwise it&lt;br/&gt;
  may not be able to access files out of its namespace).&lt;/li&gt;
	&lt;li&gt;symlink in the subdirectory will not be supported due to the extra complexity.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The following part of code will be changed:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;llite mount transverse subdirectory path.&lt;/li&gt;
	&lt;li&gt;`lfs fid2path` support subdirectory mount.&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="10371" author="laisiyao" created="Thu, 30 Dec 2010 05:14:57 +0000"  >&lt;p&gt;code ready and is being reviewed by Niu and Bobi.&lt;/p&gt;</comment>
                            <comment id="49400" author="kitwestneat" created="Tue, 18 Dec 2012 13:29:34 +0000"  >&lt;p&gt;Has there been any progress on this issue? I haven&apos;t seen anything, but I thought I&apos;d check as people have been asking about it.&lt;/p&gt;</comment>
                            <comment id="49441" author="laisiyao" created="Wed, 19 Dec 2012 06:13:40 +0000"  >&lt;p&gt;The original patch is at &lt;a href=&quot;http://review.whamcloud.com/#change,165&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,165&lt;/a&gt;, but it&apos;s not up to date. Since it&apos;s not urgent, I don&apos;t have plan to commit it soon. If someone would like to take over this work, that would be great.&lt;/p&gt;</comment>
                            <comment id="50374" author="kitwestneat" created="Fri, 11 Jan 2013 21:56:15 +0000"  >&lt;p&gt;I rebased it on master, it&apos;s here: &lt;a href=&quot;http://review.whamcloud.com/#change,5007&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,5007&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="50540" author="kitwestneat" created="Wed, 16 Jan 2013 08:31:10 +0000"  >&lt;p&gt;Thanks for the review. I&apos;m still new to Gerrit, is there someone I should add for +2?&lt;/p&gt;</comment>
                            <comment id="50541" author="pjones" created="Wed, 16 Jan 2013 08:56:24 +0000"  >&lt;p&gt;Kit&lt;/p&gt;

&lt;p&gt;No further action is needed - the patch is already in the queue for landing consideration&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="50544" author="kitwestneat" created="Wed, 16 Jan 2013 09:46:48 +0000"  >&lt;p&gt;Great, thanks&lt;/p&gt;</comment>
                            <comment id="51906" author="adilger" created="Wed, 6 Feb 2013 14:23:30 +0000"  >&lt;p&gt;What would also be very useful here for future expansion is to enhance the MDS_GETSTATUS RPC to accept a fileset name, currently always &quot;ROOT&quot;, so that this handling can be done by the MDS in the future and the &quot;traverse directory on client&quot; hack can be avoided.  That would allow completely independent filesets to be handled by different subtrees on the same MDT.  For the initial implementation, the MDT would just check for &quot;ROOT&quot; (if it is sent), and return -ENODEV if it is something else, but it would at least get clients ready for the next step.&lt;/p&gt;</comment>
                            <comment id="79877" author="sknolin" created="Thu, 20 Mar 2014 16:29:41 +0000"  >&lt;p&gt;Has this patch been held up just due to the tab/space formatting issues since last January?&lt;/p&gt;

&lt;p&gt;We are looking at working around this with bind mounts, and I ran across this patch.&lt;/p&gt;

&lt;p&gt;Scott&lt;/p&gt;</comment>
                            <comment id="79882" author="pjones" created="Thu, 20 Mar 2014 16:51:56 +0000"  >&lt;p&gt;Scott&lt;/p&gt;

&lt;p&gt;Thanks for drawing attention to this.&lt;/p&gt;

&lt;p&gt;Lai&lt;/p&gt;

&lt;p&gt;Kit has moved on to a new job. Could you please refresh the patch on his behalf?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="79959" author="laisiyao" created="Fri, 21 Mar 2014 01:27:05 +0000"  >&lt;p&gt;As Andreas suggested above, this feature should support mount with fileset name instead of &quot;traverse directory on client&quot; hack. This is not a minor change, I&apos;ll update it later.&lt;/p&gt;</comment>
                            <comment id="149249" author="gerrit" created="Sun, 17 Apr 2016 20:51:48 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/5007/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/5007/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-28&quot; title=&quot;Ability for client to mount subdirectories of a Lustre filesystem&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-28&quot;&gt;&lt;del&gt;LU-28&lt;/del&gt;&lt;/a&gt; fileset: add fileset mount support&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 9bd3e64b817ccbbf9760864b84908b87e13ebfe8&lt;/p&gt;</comment>
                            <comment id="149272" author="jgmitter" created="Mon, 18 Apr 2016 12:55:50 +0000"  >&lt;p&gt;The patch has landed to master for 2.9.0&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10323">
                    <name>Gantt End to End</name>
                                            <outwardlinks description="has to be finished together with">
                                        <issuelink>
            <issuekey id="33811">LUDOC-319</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="27803">LU-5989</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                    <customfield id="customfield_10020" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Bugzilla ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>15267.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10040" key="com.atlassian.jira.plugin.system.customfieldtypes:labels">
                        <customfieldname>Epic</customfieldname>
                        <customfieldvalues>
                                        <label>metadata</label>
            <label>mount</label>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvyh3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9769</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>