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-5906 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.hpdd.intel.com/test_sets/8190b56c-68ff-11e4-9444-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/8190b56c-68ff-11e4-9444-5254006e85c2</a>.</p> <p>The sub-test test_1d failed with the following error:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>pool_new failed lustre.testpool12345678 </pre> </div></div> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>CMD: onyx-44vm2.onyx.hpdd.intel.com lctl get_param -n lov.lustre-*.pools.testpool12345678 2&gt;/dev/null || echo foo Update not seen after 90s: wanted '' got 'foo' ost-pools test_1d: @@@@@@ FAIL: pool_new failed lustre.testpool12345678 </pre> </div></div> <p>Info required for matching: ost-pools 1d</p> server: 2.6.0<br/> client: lustre-master build #2733 LU-5906

Interop 2.6.0<->master ost-pools test_1d: FAIL: pool_new failed lustre.testpool12345678

Bug Minor Resolved Duplicate WC Triage Maloo Tue, 11 Nov 2014 19:34:43 +0000 Wed, 2 Sep 2015 18:14:36 +0000 Tue, 26 May 2015 20:40:42 +0000 Lustre 2.7.0 Lustre 2.5.3 Lustre 2.8.0 0 2 <p>It looks like this failure is caused by the landing of the following patch on master:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>commit 2305c36139a7deaf25a0dc737d412eed42ca54e9 Author: Li Xi &lt;lixi@ddn.com&gt; Date: Fri Oct 3 07:43:02 2014 +0800 LU-5054 llite: enforce pool name length limit The pool related codes have some inconsistency about the length of pool name. Creating and setting a pool name of lenght 16 to a directory will succeed. However, creating a file under that directory will fail. This patch disables any pool name which is longer or equal to 16. And it changes LOV_MAXPOOLNAME from 16 to 15 which might cause some invalid LLOG records of OST pools with 16 byte names. It is not a problem since invalid LLOG records are just ignored. And OST pools with 16 byte names won't work well anyway on the old versions. There will be problem of inconsistency if part of the servers have this patch and part of the servers don't. But it would be safe to assume that this is not a normal configuration. Signed-off-by: Li Xi &lt;lixi@ddn.com&gt; Change-Id: I3672fb5414662120c3e6b8641002a6b76994cc77 Reviewed-on: http://review.whamcloud.com/10306 </pre> </div></div> <p>I don't think this is something we will fix for b2_6, but it probably should be backported to b2_5 to avoid test failures there.</p> <p>This should be fixed in the b2_5 branch via <a href="https://jira.whamcloud.com/browse/LU-6463" title="Interop 2.5.3&lt;-&gt;master ost-pools test_1c: Pool creation of testpool12345678 failed" class="issue-link" data-issue-key="LU-6463"><del>LU-6463</del></a>, since we no longer test interop with 2.6.0.</p> Duplicate LU-6463 Development Rank 1|hzx0qv: Rank (Obsolete) 16496 Severity