<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:41:56 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>[LUDOC-313] Questions about setting up quota</title>
                <link>https://jira.whamcloud.com/browse/LUDOC-313</link>
                <project id="10070" key="LUDOC">Lustre Documentation</project>
                    <description>&lt;p&gt;Customer provided the following feedback, concerning the information provided in the current Lustre Operating Manual about how to set up quotas:&lt;/p&gt;

&lt;p&gt;&quot;My questions had to do with several issues.&lt;br/&gt;
(1) The manual lays out different approaches based on whether or not your lustre version is 2.4 or higher, but doesn&#8217;t explain how to verify what lustre version you&#8217;re using. &lt;br/&gt;
(2). The manual doesn&#8217;t make clear what server you&#8217;re supposed to run the various commands on. The section on enabling disk quotas, mentions the MGS server earlier in the section, but not lower down where it instructs you to issue the commands &#8220;lctl con_param testfs1.quota.ost=ug, and lcdl con_param testfs2.quota.mdt=g&#8221; I assumed this needed to be done on the MGS, and that seemed to work.&lt;br/&gt;
(3) At the end of the section on enabling disk quotas, the manual suggests you issue the command &#8220;lcdl get_param osd-..quota_slave.info&#8221;. I did this before enabling quotas to verify they were off, and it worked. I tried it again, on the MGS server, after enabling quotas, and got nothing but an error.&lt;br/&gt;
(4) In the section on Quota Administration, the manual makes no mention whatsoever of what server these commands should be run on. It took some thought and experimenting on my part to discover they need to be run from a lustre client, not a lustre server (correct me if I&#8217;m wrong).&lt;br/&gt;
At this point, I THINK the quotas are enabled and working properly, but I&#8217;m worried that the command I mention in (3) above is returning an error.&quot;&lt;/p&gt;</description>
                <environment></environment>
        <key id="33351">LUDOC-313</key>
            <summary>Questions about setting up quota</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="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="rhenwood">Richard Henwood</assignee>
                                    <reporter username="jfc">John Fuchs-Chesney</reporter>
                        <labels>
                            <label>quota</label>
                    </labels>
                <created>Thu, 26 Nov 2015 00:33:15 +0000</created>
                <updated>Mon, 14 Dec 2015 19:50:22 +0000</updated>
                            <resolved>Mon, 14 Dec 2015 19:50:16 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="134780" author="gerrit" created="Mon, 30 Nov 2015 21:29:30 +0000"  >&lt;p&gt;Richard Henwood (richard.henwood@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/17399&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/17399&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LUDOC-313&quot; title=&quot;Questions about setting up quota&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LUDOC-313&quot;&gt;&lt;del&gt;LUDOC-313&lt;/del&gt;&lt;/a&gt; cleanup: Remove ambiguity in quota documentation.&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 5cb7f977a1b5be3f9bd3367be54b7adb787986ae&lt;/p&gt;</comment>
                            <comment id="135548" author="jfc" created="Tue, 8 Dec 2015 19:48:47 +0000"  >&lt;p&gt;Feedback to Richard.&lt;/p&gt;

&lt;p&gt;Q 1: is addressed.&lt;/p&gt;

&lt;p&gt;Q 2: Customer is looking for explicit guidance as to which server to use for the following commands. &quot; I assumed this needed to be done on the MGS, and that seemed to work.&quot; May be worth bolding or underlining this: &quot; &lt;b&gt;all setup commands in this section must be run on the MGS.&lt;/b&gt;&quot; to make it more distinctive.&lt;/p&gt;

&lt;p&gt;Or repeat this guidance in the examples: &quot;Examples:&lt;br/&gt;
To turn on user and group quotas for block only on file system testfs1, run:$ lctl conf_param testfs1.quota.ost=ug &lt;b&gt;on the MGS server&lt;/b&gt; (assuming this is the correct guidance). Same with the other examples.&lt;/p&gt;

&lt;p&gt;Q 3: I could not locate this text &quot; &#8220;lcdl get_param osd-..quota_slave.info&#8221;.&quot; &amp;#8211; so not able to see the improvement.&lt;/p&gt;

&lt;p&gt;Q 4: If this &quot;This is controlled entirely from a client via three quota parameters&quot; is blanket guidance for the whole section I think it would be useful to highlight in some way.&lt;/p&gt;

&lt;p&gt;Thanks Richard.&lt;/p&gt;</comment>
                            <comment id="135674" author="rhenwood" created="Wed, 9 Dec 2015 17:30:07 +0000"  >&lt;p&gt;Q2, done.&lt;/p&gt;

&lt;p&gt;Q3: it is contained in section: 21.2.2.1. This command must be run on the MDS(s) - I&apos;ve emphasized this.&lt;/p&gt;

&lt;p&gt;Q4: done.&lt;/p&gt;

&lt;p&gt;Version with these changes is here:&lt;br/&gt;
&lt;a href=&quot;https://build.hpdd.intel.com/job/lustre-manual-reviews/618/artifact/lustre_manual.xhtml#configuringquotas&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://build.hpdd.intel.com/job/lustre-manual-reviews/618/artifact/lustre_manual.xhtml#configuringquotas&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="136212" author="gerrit" created="Mon, 14 Dec 2015 17:25:26 +0000"  >&lt;p&gt;Richard Henwood (richard.henwood@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/17399/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/17399/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LUDOC-313&quot; title=&quot;Questions about setting up quota&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LUDOC-313&quot;&gt;&lt;del&gt;LUDOC-313&lt;/del&gt;&lt;/a&gt; cleanup: Remove ambiguity in quota documentation.&lt;br/&gt;
Project: doc/manual&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: a591002608f4034150997adf079b7d93fa512c93&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|hzxud3:</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>