<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:42:32 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-11284] Full lock convert conflicts with HSM</title>
                <link>https://jira.whamcloud.com/browse/LU-11284</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Full lock convert is not enabled still because of conflict with HSM. Tests 33-36 and 201 in sanity-hsm.sh are failing with lock convert. This looks related to &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5216&quot; title=&quot;HSM: restore doesn&amp;#39;t restart for new copytool&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5216&quot;&gt;LU-5216&lt;/a&gt; and have to be investigated more.&lt;/p&gt;</description>
                <environment></environment>
        <key id="53121">LU-11284</key>
            <summary>Full lock convert conflicts with HSM</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</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="tappro">Mikhail Pershin</assignee>
                                    <reporter username="tappro">Mikhail Pershin</reporter>
                        <labels>
                            <label>DoM2</label>
                    </labels>
                <created>Sat, 25 Aug 2018 07:28:55 +0000</created>
                <updated>Mon, 6 Apr 2020 05:45:25 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="258300" author="tappro" created="Thu, 14 Nov 2019 14:37:24 +0000"  >&lt;p&gt;The latest patch from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11276&quot; title=&quot;racer: mdc_dev.c:1346:mdc_req_attr_set()) uncovered page&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11276&quot;&gt;&lt;del&gt;LU-11276&lt;/del&gt;&lt;/a&gt; fixes this issue. In short, the problem was in HSM code which takes server EX LAYOUT lock for restore time. During that time client can try to get file attributes which in turn will cause ll_glimpse_size0() to issue new CR LAYOUT lock to the server and be blocked by restore process.  There is workaround for this issue to prevent client from glimpsing the file being restored. It is done by returning MS_RESTORE state from server in MD attributes. The problem wasn&apos;t seen until lock convert because EX LAYOUT lock cancels client lock with all bits and usually LAYOUT bit was always combined with UPDATE bit, so client gets new attributes from server and updates restore state as needed. Lock convert keep UPDATE bit set and client uses local copy of attributes always and don&apos;t see MS_RESTORE state update. Strictly speaking this is HSM bug, because we can&apos;t always guarantee that LAYOUT is combined with UPDATE always, so problem may exists without lock convert as well.&lt;br/&gt;
Proposed solution is to take EX LAYOUT+UPDATE lock bits when restoring starts, so client states will be reset and client will need to ask attributes from server again to update restore state as expected. Note that UPDATE bit should be dropped right after EX lock is taken on server and only LAYOUT bit stay until restore will finish.&lt;/p&gt;</comment>
                            <comment id="258370" author="gerrit" created="Fri, 15 Nov 2019 13:18:29 +0000"  >&lt;p&gt;Mike Pershin (mpershin@whamcloud.com) uploaded a new patch: &lt;a href=&quot;https://review.whamcloud.com/36766&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://review.whamcloud.com/36766&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11284&quot; title=&quot;Full lock convert conflicts with HSM&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11284&quot;&gt;LU-11284&lt;/a&gt; ldlm: enable lock convert for all bits&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 345e4807cbf2fdc11dd891f4a9c1391c83c72c83&lt;/p&gt;</comment>
                            <comment id="258409" author="tappro" created="Fri, 15 Nov 2019 18:26:31 +0000"  >&lt;p&gt;There are more fixes needed, so I&apos;ve split related fixes from &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11276&quot; title=&quot;racer: mdc_dev.c:1346:mdc_req_attr_set()) uncovered page&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11276&quot;&gt;&lt;del&gt;LU-11276&lt;/del&gt;&lt;/a&gt; patch and push them under this ticket.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="25192">LU-5216</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="39596">LU-10175</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </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|i00193:</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>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>