<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:51:20 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-12297] Add an option to disable mount.lustre automatical tune</title>
                <link>https://jira.whamcloud.com/browse/LU-12297</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Mount.lustre will try to tune max_sectors_kb, scheduler automatically for OSTs in default.&lt;br/&gt;
This could cause some unexpected behavior if there are external tools which try to do same&lt;br/&gt;
things using udev rules etc, as lustre could use raw block device or be on the top of logical (N logical) devices and as a result this tunings on fly will be a result of excellent butthearts&lt;br/&gt;
especially when tuning comes from storage.&lt;/p&gt;

&lt;p&gt;In order to solve this problem, it makes sense to add a mount option like no_auto_tune&lt;br/&gt;
etc to disable automatically tune by mount.lustre util.&lt;/p&gt;</description>
                <environment></environment>
        <key id="55632">LU-12297</key>
            <summary>Add an option to disable mount.lustre automatical tune</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="3">Duplicate</resolution>
                                        <assignee username="wshilong">Wang Shilong</assignee>
                                    <reporter username="wshilong">Wang Shilong</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Tue, 14 May 2019 11:39:53 +0000</created>
                <updated>Sat, 26 Sep 2020 08:49:23 +0000</updated>
                            <resolved>Tue, 14 Jul 2020 20:38:52 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                            <comments>
                            <comment id="247111" author="gerrit" created="Tue, 14 May 2019 12:39:03 +0000"  >&lt;p&gt;&lt;del&gt;Wang Shilong (wshilong@ddn.com) uploaded a new patch:&lt;/del&gt; &lt;a href=&quot;https://review.whamcloud.com/34859&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/34859&lt;/a&gt;&lt;br/&gt;
&lt;del&gt;Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-12297&quot; title=&quot;Add an option to disable mount.lustre automatical tune&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-12297&quot;&gt;&lt;del&gt;LU-12297&lt;/del&gt;&lt;/a&gt; utils: add an option to disable mount.lustre auto tune&lt;/del&gt;&lt;br/&gt;
&lt;del&gt;Project: fs/lustre-release&lt;/del&gt;&lt;br/&gt;
&lt;del&gt;Branch: master&lt;/del&gt;&lt;br/&gt;
&lt;del&gt;Current Patch Set: 1&lt;/del&gt;&lt;br/&gt;
&lt;del&gt;Commit: 73767e5dfa772f0a3d99f3b0aa35df37b5664c8d&lt;/del&gt;&lt;/p&gt;</comment>
                            <comment id="247126" author="guzheng" created="Wed, 15 May 2019 01:45:27 +0000"  >&lt;p&gt;I think we&apos;d better to control the tune from mount_lustre rather than only ldsikfs side.&lt;br/&gt;
The major goal of this option is let lustre free from backend storage tuning, and give a chance to manage-utils or admin (out of native lustre, e.g Exascalser from DDN) who are more professional and proficient in tuning field to take over the job.&lt;br/&gt;
Actually tune to zfs is more complex than ldiskfs, and this option is also very useful to osd-zfs sites.&lt;/p&gt;</comment>
                            <comment id="247136" author="ys" created="Wed, 15 May 2019 09:15:04 +0000"  >&lt;p&gt;Hi, Shilong,&lt;/p&gt;

&lt;p&gt;I think we have a similar way to do that. Please see &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9132&quot; title=&quot;Tuning max_sectors_kb on mount&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9132&quot;&gt;&lt;del&gt;LU-9132&lt;/del&gt;&lt;/a&gt;. Also you can refer to &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-9551&quot; title=&quot;I/O errors when lustre uses multipath devices&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-9551&quot;&gt;&lt;del&gt;LU-9551&lt;/del&gt;&lt;/a&gt; for further detail. &lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Yangsheng&lt;/p&gt;</comment>
                            <comment id="247138" author="wshilong" created="Wed, 15 May 2019 09:27:34 +0000"  >&lt;p&gt;Hi Sheng,&lt;/p&gt;

&lt;p&gt;   Yup, that ticket solved some of problem that we hit currently, but isn&apos;t enough.&lt;br/&gt;
Further what want is to add a mount option disable any Lustre auto tune for ZFS/ldiskfs.&lt;/p&gt;

&lt;p&gt;For now, we want to disable max_sector_kb and scheduler tune for ldiskfs, but newly&lt;br/&gt;
tuned approach might be added in the future.&lt;/p&gt;</comment>
                            <comment id="275387" author="adilger" created="Tue, 14 Jul 2020 20:38:52 +0000"  >&lt;p&gt;Fix this via &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-12029&quot; title=&quot;do not try to muck with max_sectors_kb on multipath configurations&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-12029&quot;&gt;LU-12029&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="55014">LU-12029</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="43888">LU-9132</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="55853">LU-12387</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|i00g8n:</customfieldvalue>

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