<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:20:05 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-1833] Don&apos;t update mtab if it is symlink</title>
                <link>https://jira.whamcloud.com/browse/LU-1833</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;some distros (like Fedora 16) link /etc/mtab to /proc/mounts. In such distros, mount.lustre cannot update mtab otherwise we false alarm user with errors.&lt;/p&gt;</description>
                <environment></environment>
        <key id="15694">LU-1833</key>
            <summary>Don&apos;t update mtab if it is symlink</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="keith">Keith Mannthey</assignee>
                                    <reporter username="bergwolf">Peng Tao</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Wed, 5 Sep 2012 11:28:35 +0000</created>
                <updated>Wed, 16 Nov 2016 20:26:41 +0000</updated>
                            <resolved>Sun, 7 Oct 2012 07:27:00 +0000</resolved>
                                    <version>Lustre 2.3.0</version>
                    <version>Lustre 2.4.0</version>
                                    <fixVersion>Lustre 2.4.0</fixVersion>
                    <fixVersion>Lustre 2.1.4</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="44201" author="bergwolf" created="Wed, 5 Sep 2012 11:29:41 +0000"  >&lt;p&gt;patch submitted:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/3881&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/3881&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="46097" author="pjones" created="Sun, 7 Oct 2012 07:27:00 +0000"  >&lt;p&gt;Landed for 2.4&lt;/p&gt;</comment>
                            <comment id="48989" author="ihara" created="Mon, 10 Dec 2012 12:24:03 +0000"  >&lt;p&gt;Although this was already closed, we needed this backport patches to b2_1 and b1_8 for diskless lustre environment.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/#change,4786&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,4786&lt;/a&gt; (b1_8)&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/#change,4785&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#change,4785&lt;/a&gt; (b2_1)&lt;/p&gt;</comment>
                            <comment id="54742" author="cthomaz" created="Mon, 25 Mar 2013 09:36:06 +0000"  >&lt;p&gt;Hi.&lt;br/&gt;
Another DDN customer is concerning about this issue. Running Lustre 2.1.3&lt;br/&gt;
Any feedback if this patch will be backported to 2.1 and 1.8 versions?&lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
Carlos.&lt;/p&gt;</comment>
                            <comment id="54751" author="pjones" created="Mon, 25 Mar 2013 13:22:05 +0000"  >&lt;p&gt;Carlos&lt;/p&gt;

&lt;p&gt;This fix was included in the 2.1.4 release. Ihara has already ported the fix to b1_8 and that patch can be applied anywhere that needs it.&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="57836" author="alexxy" created="Tue, 7 May 2013 17:07:37 +0000"  >&lt;p&gt;This bug still here on 2.4&lt;br/&gt;
delta ~ # mount.lustre bootsrv@tcp:/home /home&lt;br/&gt;
mount.lustre: addmntent: Invalid argument:&lt;/p&gt;

&lt;p&gt;ls -l /etc/mtab &lt;br/&gt;
lrwxrwxrwx 1 root root 14 Jun 21  2011 /etc/mtab -&amp;gt; ../proc/mounts&lt;/p&gt;
</comment>
                            <comment id="57837" author="keith" created="Tue, 7 May 2013 17:28:44 +0000"  >&lt;p&gt;What distro are you using? &lt;/p&gt;</comment>
                            <comment id="57839" author="alexxy" created="Tue, 7 May 2013 17:34:13 +0000"  >&lt;p&gt;Gentoo. Client code was build from master + some patches to make 3.8 kernel work&lt;/p&gt;</comment>
                            <comment id="173865" author="twhitehead" created="Wed, 16 Nov 2016 16:51:31 +0000"  >&lt;p&gt;Would add that this patch doesn&apos;t work on recent fedora as systemd creates /etc/mtab as a symlink to ../proc/self/mounts which doesn&apos;t match the check for it starting with /proc/.&lt;/p&gt;

&lt;p&gt;$ readlink /etc/mtab&lt;br/&gt;
../proc/self/mounts&lt;/p&gt;

&lt;p&gt;A simple hack would be to switch to strstr to see if the symlink contains /proc/ anywhere in it or, to be 100% correct, use realpath to fully get the canonical absolute path.&lt;/p&gt;

&lt;p&gt;$ realpath /etc/mtab&lt;br/&gt;
/proc/19506/mounts&lt;/p&gt;

&lt;p&gt;Cheers!  -Tyson&lt;/p&gt;</comment>
                            <comment id="173932" author="twhitehead" created="Wed, 16 Nov 2016 20:26:41 +0000"  >&lt;p&gt;Patch to switch to from readpath to realpath.  Can confirm it works with my indirect symlink.  Haven&apos;t tested a non-symlink setup.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="16350">LU-2168</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="24096" name="0001-LU-1833-util-fully-resolve-etc-mtab-to-detect-proc-s.patch" size="1102" author="twhitehead" created="Wed, 16 Nov 2016 20:26:41 +0000"/>
                    </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|hzv5d3:</customfieldvalue>

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