<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:22:03 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-2063] HSM - Open Lock Issue</title>
                <link>https://jira.whamcloud.com/browse/LU-2063</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;This is for landing patches to master&lt;/p&gt;</description>
                <environment></environment>
        <key id="16198">LU-2063</key>
            <summary>HSM - Open Lock Issue</summary>
                <type id="6" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11315&amp;avatarType=issuetype">Story</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="jay">Jinshan Xiong</assignee>
                                    <reporter username="jlevi">Jodi Levi</reporter>
                        <labels>
                    </labels>
                <created>Mon, 1 Oct 2012 09:13:16 +0000</created>
                <updated>Tue, 29 Jan 2013 13:28:58 +0000</updated>
                            <resolved>Tue, 29 Jan 2013 13:28:58 +0000</resolved>
                                    <version>Lustre 2.4.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="47651" author="jay" created="Fri, 9 Nov 2012 14:38:23 +0000"  >&lt;p&gt;For HSM implementation, if a file is being opened, it shouldn&apos;t be picked up for release. This will have problem with open lock as the client can cache this lock for a quite long time, until there is too much cached lock on the client, or the permission of the file is changed. During the time the open lock is cached by clients, the MDT will consider this file is being opened so HSM can&apos;t pick up that file for release.&lt;/p&gt;

&lt;p&gt;The solution would be to shrink the LRU expiration time for open dlm lock so that it can be canceled earlier.&lt;/p&gt;

&lt;p&gt;The good thing is that open lock is only used for NFSD in lustre implementation. This means the problem is not that much critical, we just need to inform the CEA that HSM may not work well if lustre clients are exported for NFS use. But in the long term, we still need to solve the problem.&lt;/p&gt;</comment>
                            <comment id="51406" author="jay" created="Tue, 29 Jan 2013 13:27:51 +0000"  >&lt;p&gt;We changed the process of releasing file that we should request EX mode INODE_OPENLOCK before checking if there still exists any open handler on the MDT. This is being implemented by CEA in the file release patch. This ticket can be closed.&lt;/p&gt;</comment>
                            <comment id="51407" author="jay" created="Tue, 29 Jan 2013 13:28:14 +0000"  >&lt;p&gt;We changed the process of releasing file that we should request EX mode INODE_OPENLOCK before checking if there still exists any open handler on the MDT. This is being implemented by CEA in the file release patch. This ticket can be closed.&lt;/p&gt;</comment>
                            <comment id="51408" author="jay" created="Tue, 29 Jan 2013 13:28:35 +0000"  >&lt;p&gt;We changed the process of releasing file that we should request EX mode INODE_OPENLOCK before checking if there still exists any open handler on the MDT. This is being implemented by CEA in the file release patch. This ticket can be closed.&lt;/p&gt;</comment>
                            <comment id="51409" author="jay" created="Tue, 29 Jan 2013 13:28:58 +0000"  >&lt;p&gt;We changed the process of releasing file that we should request EX mode INODE_OPENLOCK before checking if there still exists any open handler on the MDT. This is being implemented by CEA in the file release patch. This ticket can be closed.&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_10070" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Project</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10040"><![CDATA[HSM]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzv4t3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>4312</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>