https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-16909 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="https://testing.whamcloud.com/test_sets/ea1fe5ee-03b6-4d33-9cab-ceba8caaac1a" class="external-link" target="_blank" rel="nofollow noopener">https://testing.whamcloud.com/test_sets/ea1fe5ee-03b6-4d33-9cab-ceba8caaac1a</a></p> <p>test_805 failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>DoM not working </pre> </div></div> <p>Test session details:<br/> clients: <a href="https://build.whamcloud.com/job/lustre-b2_12/164" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-b2_12/164</a> - 3.10.0-1160.49.1.el7.x86_64<br/> servers: <a href="https://build.whamcloud.com/job/lustre-b2_15/64" class="external-link" target="_blank" rel="nofollow noopener">https://build.whamcloud.com/job/lustre-b2_15/64</a> - 4.18.0-425.3.1.el8_lustre.x86_64</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>CMD: trevis-64vm4 zfs get -H quota lustre-mdt1/mdt1 CMD: trevis-64vm4 lctl get_param -n osd-zfs.lustre-MDT0000..kbytesfree CMD: trevis-64vm4 lctl get_param -n osd-zfs.lustre-MDT0000..kbytestotal CMD: trevis-64vm4 zfs set quota=102637568 lustre-mdt1/mdt1 lfs setstripe: cannot set default composite layout for '/mnt/lustre/d805.sanity': File too large sanity test_805: @@@@@@ FAIL: DoM not working </pre> </div></div> <p>VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV<br/> sanity test_805 - DoM not working</p> LU-16909

rolling-upgrade/downgrade interop: sanity test_805: DoM not working

Bug Minor Open Unresolved WC Triage Maloo ZFS Fri, 16 Jun 2023 21:57:56 +0000 Wed, 21 Jun 2023 04:03:21 +0000 Lustre 2.15.3 0 4 <p>I checked back 6 months and this is only failing with <tt>rolling-upgrade-mds-zfs</tt> and <tt>rolling-downgrade-client1-zfs</tt> (old 2.12 client, new ZFS MDS) though I haven't looked at why that is the case. The first failure was 2023-03-24, but this was the <a href="https://testing.whamcloud.com/search?test_groups%5B%5D=rolling-upgrade-mds-zfs&amp;test_set_script_id=f9516376-32bc-11e0-aaee-52540025f9ae&amp;start_date=2023-01-01&amp;end_date=2023-03-30&amp;source=test_sets#redirect" class="external-link" target="_blank" rel="nofollow noopener">first time that rolling upgrade was run</a>, so I think the problem predates this time and is not related to a bad patch landing at that time. The failure is not hit with 2.14.0-2.15.x <tt>rolling-upgrade-mds-zfs</tt> testing, so it looks like the issue was introduced sometime in the 2.13 or 2.14 development cycle.</p> Development Rank 1|i03oa7: Rank (Obsolete) 9223372036854775807 Severity