<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:02:00 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-13523] zero link directory causes crash on 2.12</title>
                <link>https://jira.whamcloud.com/browse/LU-13523</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;I have an older file system of roughly 400 million files that i&apos;m about to move to new hardware. The FS is running lustre 2.8.0 on centos 6.&lt;/p&gt;

&lt;p&gt;While traversing the file system, I found there exist some directories apparently with zero references. Here is an example such directory:&lt;/p&gt;

&lt;p&gt;drwxr-s--- 0 &amp;lt;user&amp;gt; &amp;lt;group&amp;gt; 12288 Sep 11 2016 goes3.1980.286.1915&lt;/p&gt;

&lt;p&gt;When attempting to list this directory on lustre 2.12.3 or 2.12.4 on centos 7/8 clients, it caused the system to crash. In one instance, I observed this LBUG:&lt;/p&gt;

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

&lt;p&gt;&#160;&lt;br/&gt;
 kernel:LustreError: 19084:0:(mdc_locks.c:124:mdc_set_lock_data()) ASSERTION( old_inode-&amp;gt;i_state &amp;amp; I_FREEING ) failed: Found existing inode ffff9de915cb7110/144115292816098530/0 state 0 in lock: setting data to ffff9de915cb6c90/144115292816098530/33554456Message from syslogd@s4-609-c1 at May  6 13:22:28 ...&lt;br/&gt;
 kernel:LustreError: 19084:0:(mdc_locks.c:124:mdc_set_lock_data()) LBUG&lt;br/&gt;
This does not occur on lustre 2.10.6. I downgraded to 2.10.6 and now simply receive &quot;no such file or directory&quot; instead.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment>centos 7 / centos 8</environment>
        <key id="59067">LU-13523</key>
            <summary>zero link directory causes crash on 2.12</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="wc-triage">WC Triage</assignee>
                                    <reporter username="jstroik">Jesse Stroik</reporter>
                        <labels>
                    </labels>
                <created>Wed, 6 May 2020 14:02:21 +0000</created>
                <updated>Wed, 6 May 2020 15:50:47 +0000</updated>
                                            <version>Lustre 2.12.3</version>
                    <version>Lustre 2.12.4</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                            <comments>
                            <comment id="269434" author="jstroik" created="Wed, 6 May 2020 15:50:47 +0000"  >&lt;p&gt;Looks like my formatting was lost.&lt;/p&gt;

&lt;p&gt;I tested this on&#160;lustre-client-2.13.53_99 built from git and can confirm it has this issue also.&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|i00zn3:</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>