<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:46: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-11686] sanity test 807 fails with mounted subdirectory with error &apos;/mnt/lustre/d807.sanity/single_dd expected blocks: 1, got: 0&apos; </title>
                <link>https://jira.whamcloud.com/browse/LU-11686</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;sanity test_807 verifies the LSOM syncing tool. When a Lustre client mounts a subdirectory on the Lustre file system, sanity test 807 fails and it looks like the LSOM sync tool, llsom_sync, does not return the correct information. From the failure at  &lt;a href=&quot;https://testing.whamcloud.com/test_sets/37edc450-e915-11e8-b67f-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/37edc450-e915-11e8-b67f-52540065bddc&lt;/a&gt;, the client test log contains&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;== sanity test 807: verify LSOM syncing tool ========================================================= 20:25:23 (1542313523)
&#8230;
CMD: onyx-43vm12 /usr/sbin/lctl --device lustre-MDT0000 changelog_register -n
Registered 1 changelog users: &apos;cl1&apos;
&#8230;
llite.lustre-ffff93c57c1b9000.xattr_cache=0
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.00356313 s, 294 MB/s
Test SOM for muti-client (2) writes
CMD: onyx-43vm10 multiop /mnt/lustre/f807.sanity Oz0w1048576c
CMD: onyx-43vm9.onyx.whamcloud.com multiop /mnt/lustre/f807.sanity Oz1048576w1048576c
Start to sync 3 records.
 sanity test_807: @@@@@@ FAIL: /mnt/lustre/d807.sanity/single_dd expected blocks: 1, got: 0 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;To reproduce this error, set the environment variable FILESET or, in autotest, use the test-parameter  &#8220;envdefinitions=FILESET=/subdir&#8221;. &lt;/p&gt;

&lt;p&gt;Logs for other failures are at&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/c994a85c-d3b1-11e8-9238-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/c994a85c-d3b1-11e8-9238-52540065bddc&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://testing.whamcloud.com/test_sets/71f98f92-d0a8-11e8-9238-52540065bddc&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://testing.whamcloud.com/test_sets/71f98f92-d0a8-11e8-9238-52540065bddc&lt;/a&gt;&lt;/p&gt;</description>
                <environment>subdirectory mount</environment>
        <key id="54077">LU-11686</key>
            <summary>sanity test 807 fails with mounted subdirectory with error &apos;/mnt/lustre/d807.sanity/single_dd expected blocks: 1, got: 0&apos; </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="jamesanunez">James Nunez</reporter>
                        <labels>
                            <label>LSOM</label>
                            <label>always_except</label>
                    </labels>
                <created>Wed, 21 Nov 2018 00:13:30 +0000</created>
                <updated>Mon, 22 Jan 2024 22:54:43 +0000</updated>
                                            <version>Lustre 2.12.0</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                            <comments>
                            <comment id="237289" author="pjones" created="Wed, 21 Nov 2018 00:20:13 +0000"  >&lt;p&gt;Qian&lt;/p&gt;

&lt;p&gt;Can you please advise?&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Peter&lt;/p&gt;</comment>
                            <comment id="237292" author="adilger" created="Wed, 21 Nov 2018 01:58:29 +0000"  >&lt;p&gt;This is failing because &lt;tt&gt;llapi_open_by_fid()&lt;/tt&gt; used by &lt;tt&gt;llsom_sync&lt;/tt&gt; does not work in a subdirectory mount to prevent FID-guessing attacks from within a subdir.  I suspect that this will not be an issue for real deployments, since the &lt;tt&gt;llsom_sync&lt;/tt&gt; tool would not be running inside the subdir, so it is IMHO a not a critical issue.  As a workaround, I think it would be possible to use &lt;tt&gt;llapi_fid2path()&lt;/tt&gt; within a subdirectory mount to get the proper relative pathname to open the file.  Whether that would be useful in production is a separate question.&lt;/p&gt;

&lt;p&gt;Note minor typo in test_807 - &quot;muti&quot; -&amp;gt; &quot;multi&quot; in a few places.&lt;/p&gt;

&lt;p&gt;Also, in &lt;tt&gt;llsom_sync.c&lt;/tt&gt; it defines &lt;tt&gt;PATH_MAX&lt;/tt&gt; but doesn&apos;t use it anywhere.&lt;/p&gt;</comment>
                            <comment id="400667" author="adilger" created="Mon, 22 Jan 2024 22:54:25 +0000"  >&lt;p&gt;Currently, sanity.sh test_807 is skipped when &lt;tt&gt;FILESET&lt;/tt&gt; is set, but I suspect this is now fixed by &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8585&quot; title=&quot;All Lustre test suites should pass with subdirectory mount&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8585&quot;&gt;LU-8585&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="400668" author="adilger" created="Mon, 22 Jan 2024 22:54:43 +0000"  >&lt;p&gt;Need to re-enable this subtest and see if it is passing.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                        <issuelink>
            <issuekey id="39648">LU-8585</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|i006p3:</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>