<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:07:29 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-483] Lustre quota not usabe</title>
                <link>https://jira.whamcloud.com/browse/LU-483</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>
&lt;p&gt;The CEA Bull customer is complaining about quota that are not working properly with Luster 2.0 Bull.&lt;br/&gt;
Until last week, quota were disabled because they were experiencing frequent system crashes on some IO servers.&lt;br/&gt;
We delivered an Efix containing the patch proposed in &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-369&quot; title=&quot;ASSERTION(oti &amp;amp;&amp;amp; oti-&amp;gt;oti_thread &amp;amp;&amp;amp; oti-&amp;gt;oti_thread-&amp;gt;t_watchdog) failed in quota_chk_acq_common()&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-369&quot;&gt;&lt;del&gt;LU-369&lt;/del&gt;&lt;/a&gt;, and they re-enabled quota and made some tests.&lt;br/&gt;
There is no longer system crashes, but a user is able to write more than allowed by quotas.&lt;/p&gt;

&lt;p&gt;Here is the description of there tests:&lt;br/&gt;
 1. starting of the fs&lt;br/&gt;
 2. quotaoff/quotacheck/quotaon/quotacheck&lt;br/&gt;
 3. set the quota to a user who has already exceeded it&apos;s quota&lt;br/&gt;
 4. this user is able to continue to write&lt;br/&gt;
 5. set the user quota to a value higher than the actual used capacity&lt;br/&gt;
 6. this user is able to write and to exceed is quota&lt;/p&gt;

&lt;p&gt;I attached the syslog of the IO servers they provided (MDS:curie113, OSS:curie200-207).&lt;/p&gt;</description>
                <environment></environment>
        <key id="11274">LU-483</key>
            <summary>Lustre quota not usabe</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="johann">Johann Lombardi</assignee>
                                    <reporter username="patrick.valentin">Patrick Valentin</reporter>
                        <labels>
                    </labels>
                <created>Tue, 5 Jul 2011 10:32:39 +0000</created>
                <updated>Mon, 10 Oct 2011 10:31:16 +0000</updated>
                            <resolved>Mon, 10 Oct 2011 10:31:16 +0000</resolved>
                                    <version>Lustre 2.0.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="17249" author="johann" created="Tue, 5 Jul 2011 10:59:23 +0000"  >&lt;p&gt;&amp;gt; Here is the description of there tests:&lt;br/&gt;
&amp;gt; 1. starting of the fs&lt;br/&gt;
&amp;gt; 2. quotaoff/quotacheck/quotaon/quotacheck&lt;br/&gt;
&amp;gt; 3. set the quota to a user who has already exceeded it&apos;s quota&lt;br/&gt;
&amp;gt; 4. this user is able to continue to write&lt;/p&gt;

&lt;p&gt;Please note that there is no integration between the data writeback cache and quota. This means that a user can overrun his quota limit, up to #clients x #OSC x max_dirty_mb in the worst case scenario.&lt;br/&gt;
Could you please tell us how much data you tried to write? Do you eventually get&quot;quota exceeded&quot; if you write more than 32MB from one client? Could you please give us the output of lfs quota -u $username?&lt;/p&gt;</comment>
                            <comment id="17446" author="patrick.valentin" created="Fri, 8 Jul 2011 04:13:00 +0000"  >&lt;p&gt;Hi Johan,&lt;/p&gt;

&lt;p&gt;I got in touch with our on-site support and it seems it was a copy of about 1 Tb.&lt;br/&gt;
They will transmit your questions to the customer.&lt;/p&gt;

&lt;p&gt;Patrick&lt;/p&gt;</comment>
                            <comment id="17603" author="sebastien.buisson" created="Tue, 12 Jul 2011 08:31:24 +0000"  >&lt;p&gt;No news from the customer since last Friday.&lt;/p&gt;</comment>
                            <comment id="18048" author="sebastien.buisson" created="Thu, 21 Jul 2011 11:19:09 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Is there any way to check per-OST quota accounting? An internal file stored in the MDT or in each OST for instance?&lt;br/&gt;
That would help this problem&apos;s diagnostic.&lt;/p&gt;

&lt;p&gt;TIA,&lt;br/&gt;
Sebastien.&lt;/p&gt;</comment>
                            <comment id="18049" author="johann" created="Thu, 21 Jul 2011 11:24:08 +0000"  >&lt;p&gt;Sure, lfs quota -uv $username /path should return those info.&lt;/p&gt;</comment>
                            <comment id="21035" author="johann" created="Mon, 10 Oct 2011 09:46:07 +0000"  >&lt;p&gt;Any news or shall we just close this bug? Please advise.&lt;/p&gt;</comment>
                            <comment id="21041" author="patrick.valentin" created="Mon, 10 Oct 2011 10:09:22 +0000"  >&lt;p&gt;After one of the latest CEA EFIX installation, in the course of september, they made some quota tests and it seems to work correctly.&lt;br/&gt;
This ticket can be closed as it was not reproduced (probably a system which was not at the latest EFIX level).&lt;br/&gt;
Cheers&lt;/p&gt;</comment>
                            <comment id="21042" author="pjones" created="Mon, 10 Oct 2011 10:31:16 +0000"  >&lt;p&gt;Good news! Thanks Patrick!&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="10294" name="syslog.curie.gz" size="817216" author="patrick.valentin" created="Tue, 5 Jul 2011 10:32:39 +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|hzvi5b:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>6589</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>