<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:51:49 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-12351] quota not enforced on chgrp</title>
                <link>https://jira.whamcloud.com/browse/LU-12351</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;On today&apos;s master, if group quotas are on and a normal user creates files as one group then does a chgrp to a second one, group quotas are not enforced at all for the second group (inode or block).&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5152&quot; title=&quot;Can&amp;#39;t enforce block quota when unprivileged user change group&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5152&quot;&gt;&lt;del&gt;LU-5152&lt;/del&gt;&lt;/a&gt; fixed this issue at some point with 8a71fd5061 (&quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5152&quot; title=&quot;Can&amp;#39;t enforce block quota when unprivileged user change group&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5152&quot;&gt;&lt;del&gt;LU-5152&lt;/del&gt;&lt;/a&gt; quota: enforce block quota for chgrp&quot;), but 7b46ff54afb23 (&quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5152&quot; title=&quot;Can&amp;#39;t enforce block quota when unprivileged user change group&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5152&quot;&gt;&lt;del&gt;LU-5152&lt;/del&gt;&lt;/a&gt; quota: disable sync chgrp to OSTs&quot;) broke the fix - reverting that commit makes chgrp fail with EDQUOT as expected but the patch was introduced because of some deadlock between OST and MDT so we cannot just revert it.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;I stumbled into this again because we have quite a few users that are over quota on our long-term filesystems and I believe the reason to be... rsync.&lt;/p&gt;

&lt;p&gt;Our users create their files in a scratch, then rsync -a their files over to the longer term FS; rsync will create the files under their primary group then chgrp it, letting them make more files despite having long overrun the limits. (we normally have the group sticky bit set so files should be created with the correct group right away, I need to look a bit more into this, but anyway...)&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Splitting this into two sides:&lt;/p&gt;

&lt;p&gt;&#160;* inode quota: that is enforced directly by MDTs so should possible to re-introduce synchronous check without deadlocks? Frankly speaking this is the most important part for me.&lt;/p&gt;

&lt;p&gt;&#160;* block quota: I can imagine this will be difficult to fix properly, especially wrt. performance, but we don&apos;t really need a precise limit. As a thought, it might be possible to not do this synchronously but just check if the group already is over quota somehow and deny further user-induced chgrps in this case? I don&apos;t really know if MDTs already are aware of anything on this side, but since they should be responsible to distribute qunits to osts I believe they should?&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;( and third point: add tests for this!)&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

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

&lt;p&gt;Dominique&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment></environment>
        <key id="55777">LU-12351</key>
            <summary>quota not enforced on chgrp</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="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="hongchao.zhang">Hongchao Zhang</assignee>
                                    <reporter username="cealustre">CEA</reporter>
                        <labels>
                    </labels>
                <created>Wed, 29 May 2019 09:22:17 +0000</created>
                <updated>Wed, 5 Aug 2020 13:27:56 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="247935" author="pjones" created="Wed, 29 May 2019 12:47:08 +0000"  >&lt;p&gt;Hongchao&lt;/p&gt;

&lt;p&gt;Can you please investigate?&lt;/p&gt;

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

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="248511" author="hongchao.zhang" created="Thu, 6 Jun 2019 09:02:14 +0000"  >&lt;p&gt;the patch &lt;a href=&quot;https://review.whamcloud.com/33996&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/33996&lt;/a&gt; is just updated and tracked at &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11303&quot; title=&quot;slow chgrp as user when quotas are enabled&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11303&quot;&gt;&lt;del&gt;LU-11303&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="248516" author="martinetd" created="Thu, 6 Jun 2019 09:31:29 +0000"  >&lt;p&gt;Thanks Hongchao, I&apos;ll have a look at the code and comment on gerrit.&lt;/p&gt;

&lt;p&gt;I just tested the patch first and it does restore functionality for block quota but not inode quota, it&apos;s probably missing some detail.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="53159">LU-11303</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|i00h4v:</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>
                                                                                            <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>