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-3794 Lustre <p>This issue was created by maloo for Nathaniel Clark &lt;nathaniel.l.clark@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/c242b946-0949-11e3-b004-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/c242b946-0949-11e3-b004-52540035b04c</a>.</p> <p>The sub-test test_73 failed with the following error:</p> <blockquote> <p>1st tunefs failed</p></blockquote> <p>Info required for matching: conf-sanity 73</p> LU-3794

conf-sanity test_73: 1st tunefs failed

Bug Minor Resolved Duplicate WC Triage Maloo revzfs zfs Tue, 20 Aug 2013 18:10:58 +0000 Wed, 21 Aug 2013 16:51:32 +0000 Wed, 21 Aug 2013 16:51:32 +0000 Lustre 2.5.0 0 3 <p>Looks like this test fails after previous tests fail. They may leave the nodes mounted thus causing tunefs.lustre to fail.</p> <p>This is roughly the same issue as <a href="https://jira.whamcloud.com/browse/LU-3793" title="conf-sanity, subtest test_66 fails due to previous state" class="issue-link" data-issue-key="LU-3793"><del>LU-3793</del></a></p> <p>Closing as a duplicate of <a href="https://jira.whamcloud.com/browse/LU-3793" title="conf-sanity, subtest test_66 fails due to previous state" class="issue-link" data-issue-key="LU-3793"><del>LU-3793</del></a>. It is OK to have this bug to help track failures of this specific test number, but it only makes sense to keep one of them open to track fixing conf-sanity to be more robust in the face of failure.</p> Related LU-3793 Development Rank 1|hzvyon: Rank (Obsolete) 9811 Severity