<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:37:37 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-3868] lockless IO does not update inode timestamps</title>
                <link>https://jira.whamcloud.com/browse/LU-3868</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;In osc_io_read_start() and osc_io_write_start() if the lockless IO bit is set in the osc_io then the inode timestamps are not updated by the IO. Is there any reason for this?&lt;/p&gt;

&lt;p&gt;In osc_io_write_start() we have the following unnecessary attr get before we set the m- and c-times?&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;                result = cl_object_attr_get(env, obj, attr);
                if (result == 0) {
			attr-&amp;gt;cat_mtime = attr-&amp;gt;cat_ctime =
                                LTIME_S(CFS_CURRENT_TIME);
                        result = cl_object_attr_set(env, obj, attr,
                                                    CAT_MTIME | CAT_CTIME);
                }
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="20736">LU-3868</key>
            <summary>lockless IO does not update inode timestamps</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="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="wc-triage">WC Triage</assignee>
                                    <reporter username="jhammond">John Hammond</reporter>
                        <labels>
                            <label>osc</label>
                            <label>patch</label>
                    </labels>
                <created>Fri, 30 Aug 2013 19:13:22 +0000</created>
                <updated>Tue, 20 May 2014 13:49:54 +0000</updated>
                            <resolved>Tue, 20 May 2014 13:49:54 +0000</resolved>
                                    <version>Lustre 2.5.0</version>
                                    <fixVersion>Lustre 2.6.0</fixVersion>
                    <fixVersion>Lustre 2.5.2</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="65473" author="jhammond" created="Fri, 30 Aug 2013 19:16:35 +0000"  >&lt;p&gt;Vladimir and Vitaly, I see that you wrote and inspected this code. Could you explain why we would not update timestamps for lockless IO?&lt;/p&gt;</comment>
                            <comment id="65584" author="vitaly_fertman" created="Tue, 3 Sep 2013 09:59:29 +0000"  >&lt;p&gt;timestamps cached on client, as well as other attributes, have no sense without locks, so no need to set it for lockless IO, client just passes attributes to server.&lt;br/&gt;
if there is a raced locked IO, its lock will be cancelled by server-side lock taken by lockless IO and next attempt of acquiring a lock will bring proper attributes on client.&lt;br/&gt;
btw, it concerns truncate as well.&lt;/p&gt;</comment>
                            <comment id="65751" author="adilger" created="Wed, 4 Sep 2013 16:39:32 +0000"  >&lt;p&gt;There is no requirement that the server clocks are in sync with the client clocks, so all file timestamps should be generated by the client.  In the case of lockless IO, there should be a timestamp update sent by the client with each RPC, regardless of whether it is cached under a DLM lock by the client or not.&lt;/p&gt;</comment>
                            <comment id="74733" author="spimpale" created="Fri, 10 Jan 2014 12:17:09 +0000"  >&lt;p&gt;Patch: &lt;a href=&quot;http://review.whamcloud.com/8797&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/8797&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="84441" author="pjones" created="Tue, 20 May 2014 13:49:54 +0000"  >&lt;p&gt;Landed for 2.5.2 and 2.6&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="20599">LU-3832</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|hzvzrj:</customfieldvalue>

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