<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:51:42 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-12337] SoM in DoM needs to work transparently</title>
                <link>https://jira.whamcloud.com/browse/LU-12337</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;If all data are in DoM (no other components in OSTs), file size should be already stored into MDT object because of DoM.&lt;br/&gt;
 It doesn&apos;t need SoM with DoM, but &apos;lfs getsom&apos; needs to work transparently same as non-DoM files.&lt;br/&gt;
 Here is an issue of &apos;lfs getsom&apos; with DoM.&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;[root@c01 ~]# mkdir /cache1/dom
[root@c01 ~]# lfs setstripe -L mdt -E 2M /cache1/dom
[root@c01 ~]# pdsh -w c[01-02] lctl set_param ldlm.namespaces.*.lru_size=clear
[root@c01 ~]# pdsh -w es400nv-vm[1-4] &quot;echo 3 &amp;gt; /proc/sys/vm/drop_caches&quot;
[root@c01 ~]# lctl get_param ldlm.namespaces.*MDT0000*.lock_count
ldlm.namespaces.cache1-MDT0000-mdc-ffff97f3bc25d000.lock_count=0

Create an file on c01
[root@c01 ~]# dd if=/dev/zero of=/cache1/dom/file bs=1M count=1
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00162115 s, 647 MB/s

Run &apos;lfs getsom&apos; on c02 (different client)
[root@c02 ~]# lfs getsom -s /cache1/nondom/file
/cache1/nondom/file failed to get som xattr: No such file or directory (2)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Also, even &apos;lfs getsom&apos; works with DoM, we don&apos;t want lock cancellation for OST objects after fetch SOM.&lt;br/&gt;
 Please see below SoM for non-DoM configuration.&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;[root@c01 ~]# mkdir /cache1/nondom
[root@c01 ~]# lfs setstripe -i 0 /cache1/nondom/
[root@c01 ~]# pdsh -w c[01-02] lctl set_param ldlm.namespaces.*.lru_size=clear
[root@c01 ~]# pdsh -w es400nv-vm[1-4] &quot;echo 3 &amp;gt; /proc/sys/vm/drop_caches&quot;

[root@c01 ~]# lctl get_param ldlm.namespaces.*0000*.lock_count
ldlm.namespaces.cache1-MDT0000-mdc-ffff97f3bc25d000.lock_count=0
ldlm.namespaces.cache1-OST0000-osc-ffff97f3bc25d000.lock_count=0

Create an file on c01
[root@c01 ~]# dd if=/dev/zero of=/cache1/nondom/file bs=1M count=1
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00185952 s, 564 MB/s
[root@c01 ~]#  lctl get_param ldlm.namespaces.*0000*.lock_count
ldlm.namespaces.cache1-MDT0000-mdc-ffff97f3bc25d000.lock_count=3
ldlm.namespaces.cache1-OST0000-osc-ffff97f3bc25d000.lock_count=1

Even run &apos;lfs getsom&apos; on c02, no lock cancellation on c01
[root@c02 ~]# lfs getsom -s /cache1/nondom/file
[root@c01 ~]# lctl get_param ldlm.namespaces.*0000*.lock_count
ldlm.namespaces.cache1-MDT0000-mdc-ffff97f3bc25d000.lock_count=3
ldlm.namespaces.cache1-OST0000-osc-ffff97f3bc25d000.lock_count=1
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment>master</environment>
        <key id="55750">LU-12337</key>
            <summary>SoM in DoM needs to work transparently</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="sihara">Shuichi Ihara</reporter>
                        <labels>
                    </labels>
                <created>Fri, 24 May 2019 23:14:12 +0000</created>
                <updated>Mon, 22 Feb 2021 21:58:59 +0000</updated>
                            <resolved>Mon, 22 Feb 2021 21:58:59 +0000</resolved>
                                    <version>Lustre 2.13.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="247678" author="adilger" created="Sat, 25 May 2019 01:41:01 +0000"  >&lt;p&gt;For &lt;tt&gt;lfs getsom&lt;/tt&gt; I don&apos;t really want this to be the primary interface for accessing SOM data, but I agree it makes sense to be consistent. For DoM file&apos;s it should be possible to generate a fake &lt;tt&gt;trusted.som&lt;/tt&gt; xattr on the client based on the in-memory size.&lt;/p&gt;
</comment>
                            <comment id="272578" author="adilger" created="Thu, 11 Jun 2020 08:45:26 +0000"  >&lt;p&gt;Shuichi, IMHO &quot;&lt;tt&gt;lfs getsom&lt;/tt&gt;&quot; shouldn&apos;t be more than a debugging tool for testing.  We now have proper LSOM access via &lt;tt&gt;statx()&lt;/tt&gt;, and &quot;&lt;tt&gt;lfs find -lazy&lt;/tt&gt;&quot;, and if &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11962&quot; title=&quot;File LSOM updates to store proper size via FLR for regular stat() usage&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11962&quot;&gt;LU-11962&lt;/a&gt; is implemented we could have proper SOM for normal &quot;&lt;tt&gt;stat()&lt;/tt&gt;&quot; calls for files that are not being modified.&lt;/p&gt;

&lt;p&gt;I&apos;d rather spend effort on &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-11962&quot; title=&quot;File LSOM updates to store proper size via FLR for regular stat() usage&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-11962&quot;&gt;LU-11962&lt;/a&gt; than making &quot;&lt;tt&gt;lfs getsom&lt;/tt&gt;&quot; work for DoM files.  What do you think?&lt;/p&gt;</comment>
                            <comment id="292583" author="adilger" created="Mon, 22 Feb 2021 09:00:11 +0000"  >&lt;p&gt;Mike, I think that this is now the case, that if the DoM component is the only initialized component of the file, then the MDS returns the size to the client for &lt;tt&gt;stat()&lt;/tt&gt;?&lt;/p&gt;</comment>
                            <comment id="292624" author="tappro" created="Mon, 22 Feb 2021 15:48:57 +0000"  >&lt;p&gt;Andreas, yes, MDS returns DoM size to a client&lt;/p&gt;</comment>
                            <comment id="292687" author="adilger" created="Mon, 22 Feb 2021 21:58:59 +0000"  >&lt;p&gt;I think this was fixed as part of the statx() patches.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="54867">LU-11962</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="53281">LU-11367</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|i00gyv:</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>