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-15841] sanity-flr test 47 is failing with 'component 65537, 131075, 196613 have objects allocated on duplicated OSTs' https://jira.whamcloud.com/browse/LU-15841 Lustre <p>sanity-flr test_47 fails with 'component 65537, 131075, 196613 have objects allocated on duplicated OSTs'.</p> <p>CentOS 7.9: <a href="https://testing.whamcloud.com/test_sets/070f71ca-c788-41b1-a76b-1142434473d2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/070f71ca-c788-41b1-a76b-1142434473d2</a></p> <p>SLES15 SP3 clients: <a href="https://testing.whamcloud.com/test_sets/71b07e54-1802-4a2a-86e7-1268e89c8e1d" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/71b07e54-1802-4a2a-86e7-1268e89c8e1d</a></p> <p>CentOS 8.5 clients: <a href="https://testing.whamcloud.com/test_sets/c0006263-2d3b-4420-b47b-237e2d6257d0" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/c0006263-2d3b-4420-b47b-237e2d6257d0</a></p> LU-15841 sanity-flr test 47 is failing with 'component 65537, 131075, 196613 have objects allocated on duplicated OSTs' Bug Major Resolved Fixed Zhenyu Xu Zhenyu Xu Wed, 11 May 2022 10:31:02 +0000 Mon, 6 Jun 2022 13:32:55 +0000 Mon, 6 Jun 2022 13:32:55 +0000 Lustre 2.16.0 0 3 <p>"Bobi Jam &lt;bobijam@hotmail.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/47293" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/47293</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15841" title="sanity-flr test 47 is failing with &#39;component 65537, 131075, 196613 have objects allocated on duplicated OSTs&#39;" class="issue-link" data-issue-key="LU-15841"><del>LU-15841</del></a> lod: iterate component to collect avoid array<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: d04b04056e45edc95117f0761359ddc4637d3f37</p> <p>Is there a reason this test just started failing? I see there is a "<tt>Fixes: fabf3fe7</tt>" label on the patch, but that patch was landed as commit v2_11_53_0-18-gfabf3fe7ac (i.e. before FLR was even released), so it seems there must be some other reason this test is recently failing.</p> <p>Coincidentally I just filed <a href="https://jira.whamcloud.com/browse/LU-15843" title="Crash when umount mdt targets lnet with llstat running." class="issue-link" data-issue-key="LU-15843">LU-15843</a> on this same topic.</p> <p>Usually the OST object allocation policy would choose OSTs sequentially one by one even accounting to a new mirror so that in most occasions the test passes, and I don't know why recently it choose an already-chosen OST sometimes for a new mirror.</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/47293/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/47293/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15841" title="sanity-flr test 47 is failing with &#39;component 65537, 131075, 196613 have objects allocated on duplicated OSTs&#39;" class="issue-link" data-issue-key="LU-15841"><del>LU-15841</del></a> lod: iterate component to collect avoid array<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 7f157f8ef374c4fc3dec6a91a29f4bf15b5e0969</p> <p>Landed for 2.16</p> Duplicate Related LU-15834 LU-9007 Development Rank 1|i02plz: Rank (Obsolete) 9223372036854775807 Severity