<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:49:57 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-5262] setfacl on striped directory will cause the striped directory crash</title>
                <link>https://jira.whamcloud.com/browse/LU-5262</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The mdd_acl_set() sets size unexpectedly on the master object and cause the master object&apos;s directory content is truncated.&lt;/p&gt;

&lt;p&gt;This corruption can be easily reproduced by the sanity test_125, unfortunately, there is no way to read the master object directory content directly until we work on the patch for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5223&quot; title=&quot;generate DNE stripe directory LMV EA dynamically via readdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5223&quot;&gt;&lt;del&gt;LU-5223&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</description>
                <environment></environment>
        <key id="25339">LU-5262</key>
            <summary>setfacl on striped directory will cause the striped directory crash</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</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="yong.fan">nasf</assignee>
                                    <reporter username="yong.fan">nasf</reporter>
                        <labels>
                            <label>HB</label>
                    </labels>
                <created>Fri, 27 Jun 2014 10:21:11 +0000</created>
                <updated>Wed, 2 Jul 2014 00:01:03 +0000</updated>
                            <resolved>Wed, 2 Jul 2014 00:01:03 +0000</resolved>
                                                    <fixVersion>Lustre 2.6.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="87674" author="adilger" created="Fri, 27 Jun 2014 10:39:51 +0000"  >&lt;p&gt;Isn&apos;t the fix here to clear LA_SIZE (and most others except LA_MODE) from attr-&amp;gt;la_valid bits in mdd_xattr_set() before mdo_attr_set() is called so that these values are not all changed?  Otherwise, there is a chance that this will set stale values into the inode if it is changed concurrently (e.g. pdirops).  It isn&apos;t clear why &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5223&quot; title=&quot;generate DNE stripe directory LMV EA dynamically via readdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5223&quot;&gt;&lt;del&gt;LU-5223&lt;/del&gt;&lt;/a&gt; is needed to fix this?&lt;/p&gt;</comment>
                            <comment id="87680" author="yong.fan" created="Fri, 27 Jun 2014 11:42:50 +0000"  >&lt;p&gt;Here is the patch:&lt;br/&gt;
&lt;a href=&quot;http://review.whamcloud.com/10870&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/10870&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It is an important patch, should be landed to Lustre-2.6&lt;/p&gt;</comment>
                            <comment id="87682" author="yong.fan" created="Fri, 27 Jun 2014 12:23:52 +0000"  >&lt;p&gt;The basic idea of the patch is that: &quot;NOT set size on directory&quot;.&lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5223&quot; title=&quot;generate DNE stripe directory LMV EA dynamically via readdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5223&quot;&gt;&lt;del&gt;LU-5223&lt;/del&gt;&lt;/a&gt; depends on this patch, because if without the patch, the master object may be truncated unexpectedly when setfacl, then the iteration the master object to build LMV EA will get failure because the master directory (for shards FID and name) will be regarded empty although it is not empty.&lt;/p&gt;

&lt;p&gt;Sanity test_125 test such case, that is why &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5223&quot; title=&quot;generate DNE stripe directory LMV EA dynamically via readdir&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5223&quot;&gt;&lt;del&gt;LU-5223&lt;/del&gt;&lt;/a&gt; failed at sanity.&lt;/p&gt;</comment>
                            <comment id="87684" author="bzzz" created="Fri, 27 Jun 2014 12:38:20 +0000"  >&lt;p&gt;probably it makes sense to check in OSD for LA_SIZE in case of non-regular file.&lt;/p&gt;</comment>
                            <comment id="87690" author="yong.fan" created="Fri, 27 Jun 2014 14:40:00 +0000"  >&lt;p&gt;Then all OSDs need to check LA_SIZE. Why not control that in MDD/LOD, then no need to worry about new OSD in future.&lt;/p&gt;</comment>
                            <comment id="87707" author="bzzz" created="Fri, 27 Jun 2014 16:46:43 +0000"  >&lt;p&gt;MDD/LOD/OFD should not try to do this of course. I&apos;m saying about something more like LASSERT() in OSD.&lt;/p&gt;</comment>
                            <comment id="87748" author="di.wang" created="Sat, 28 Jun 2014 02:24:23 +0000"  >&lt;p&gt;Ah it seems the problem is that in lod_attr_get, it tries to merge the size from all sub-stripes, then in lod_attr_set it set the merged size to master object. &lt;br/&gt;
probably we can just simply drop the merging in lod_attr_get, which is actually unnecessary, see &lt;a href=&quot;http://review.whamcloud.com/#/c/10841/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/#/c/10841/&lt;/a&gt;  And this will also fix &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5130&quot; title=&quot;Test failure sanity test_17n: destroy remote dir error 0&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5130&quot;&gt;&lt;del&gt;LU-5130&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="87932" author="yong.fan" created="Wed, 2 Jul 2014 00:01:03 +0000"  >&lt;p&gt;The patch has been landed to master&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|hzwq2n:</customfieldvalue>

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