Whamcloud Community JIRA https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 [LU-3741] SLES11SP2 server,Failure on test suite sanityn test_16 https://jira.whamcloud.com/browse/LU-3741 Lustre <p>This issue was created by maloo for sarah &lt;sarah@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/10fb6bd4-00c4-11e3-b06c-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/10fb6bd4-00c4-11e3-b06c-52540035b04c</a>.</p> <p>The sub-test test_16 failed with the following error:</p> <blockquote> <p>test_16 returned 1</p></blockquote> <p>Info required for matching: sanityn 16</p> LU-3741 SLES11SP2 server,Failure on test suite sanityn test_16 Bug Critical Resolved Low Priority Bob Glossman Maloo Tue, 13 Aug 2013 01:52:30 +0000 Thu, 9 Jan 2020 07:15:21 +0000 Thu, 9 Jan 2020 07:15:21 +0000 Lustre 2.6.0 0 9 <p>Niu/Jinshan,<br/> could one of you please have a look at this? This is an fsx data corruption.<br/> Thank you!</p> <p><a href="https://jira.whamcloud.com/browse/LU-3743" title="SLES11SP2 server,Failure on test suite sanity-benchmark test_fsx" class="issue-link" data-issue-key="LU-3743"><del>LU-3743</del></a> looks not duplicated of this one: This ticket is about SLES client fsx mmap read error, however, <a href="https://jira.whamcloud.com/browse/LU-3743" title="SLES11SP2 server,Failure on test suite sanity-benchmark test_fsx" class="issue-link" data-issue-key="LU-3743"><del>LU-3743</del></a> is about RHEL client (SLES server) fsx read error. I copied the maloo link of <a href="https://jira.whamcloud.com/browse/LU-3743" title="SLES11SP2 server,Failure on test suite sanity-benchmark test_fsx" class="issue-link" data-issue-key="LU-3743"><del>LU-3743</del></a> here for reference: <a href="https://maloo.whamcloud.com/test_sets/ab5e3332-00c4-11e3-b06c-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/ab5e3332-00c4-11e3-b06c-52540035b04c</a></p> <p>The <a href="https://jira.whamcloud.com/browse/LU-3743" title="SLES11SP2 server,Failure on test suite sanity-benchmark test_fsx" class="issue-link" data-issue-key="LU-3743"><del>LU-3743</del></a> looks likely another instance of <a href="https://jira.whamcloud.com/browse/LU-2304" title="Test failure sanityn test_16: dual-mount fsx data read error" class="issue-link" data-issue-key="LU-2304"><del>LU-2304</del></a>. Xiong, any idea?</p> <p>Lustre build: <a href="http://build.whamcloud.com/job/lustre-reviews/20841/" class="external-link" target="_blank" rel="nofollow noopener">http://build.whamcloud.com/job/lustre-reviews/20841/</a><br/> Distro/Arch: SLES11SP3/x86_64 (both server and client)</p> <p>sanity-benchmark test fsx hit the same failure:<br/> <a href="https://maloo.whamcloud.com/test_sets/dd8224e0-7987-11e3-a27b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/dd8224e0-7987-11e3-a27b-52540035b04c</a></p> <p>FYI, the last time I checked, all fsx based tests fail with SLES11SP<span class="error">&#91;23&#93;</span> OSS using ldiskfs, regardless of client type. I have not tested using zfs, but I suspect the problem is with corruption following write after truncate in the ldiskfs derived from SLES ext4 source. </p> <p>Close old bug</p> Related LU-3743 Development Rank 1|hzvxsn: Rank (Obsolete) 9658 Severity