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-1006] Test failure on test suite conf-sanity https://jira.whamcloud.com/browse/LU-1006 Lustre <p>This issue was created by maloo for Peter Jones &lt;pjones@whamcloud.com&gt;</p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/139efa48-410a-11e1-972d-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/139efa48-410a-11e1-972d-5254004bbbd3</a>.</p> LU-1006 Test failure on test suite conf-sanity Bug Blocker Resolved Fixed Niu Yawei Maloo Tue, 17 Jan 2012 08:57:35 +0000 Fri, 27 Jan 2012 17:49:07 +0000 Fri, 27 Jan 2012 17:49:07 +0000 Lustre 2.2.0 0 3 <p>Niu</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>The debug log shows</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">== conf-sanity test 56: check big indexes == 16:39:05 (1326760745) fat-intel-3vm7: fat-intel-3vm7: mkfs.lustre FATAL: Unable to build fs /dev/lvm-MDS/P0 (256) fat-intel-3vm7: fat-intel-3vm7: mkfs.lustre FATAL: mkfs failed 256 Permanent disk data: Target: lustre-MDTffff Index: unassigned Lustre FS: lustre Mount type: ldiskfs Flags: 0x75 (MDT MGS needs_index first_time update ) Persistent mount opts: errors=remount-ro,iopen_nopriv,user_xattr,acl Parameters: sys.timeout=20 device size = 29596MB formatting backing filesystem ldiskfs on /dev/lvm-MDS/P0 target name lustre-MDTffff 4k blocks 10000 options -J size=16 -I 512 -i 2048 -q -O dirdata,uninit_bg,dir_nlink,huge_file,flex_bg -E lazy_journal_init -F mkfs_cmd = mke2fs -j -b 4096 -L lustre-MDTffff -J size=16 -I 512 -i 2048 -q -O dirdata,uninit_bg,dir_nlink,huge_file,flex_bg -E lazy_journal_init -F /dev/lvm-MDS/P0 10000 Journal size too big <span class="code-keyword">for</span> filesystem. </pre> </div></div> <p>The mkfs for mds device failed, I think it should be testing environment problem.</p> <p>Hi, Chris</p> <p>Could you take a look to see why the mkfs for /dev/lvm-MDS/P0 on fat-intel-3vm7 failed? Thanks.</p> <p>Looks it's duplicated with <a href="https://jira.whamcloud.com/browse/LU-544" title="1.8&lt;-&gt;2.1 interop: conf-sanity test 56: mkfs.lustre FAIL: Journal size too big for filesystem." class="issue-link" data-issue-key="LU-544"><del>LU-544</del></a>:</p> <p>We are making filesystem with 16M journal size on a ~39M mds device, why the mds size is so small? Yujian/Chris, could you take a look? Thanks.</p> <p>Hi Chris,<br/> From the Maloo report, I saw the b1_8 build was <a href="http://build.lab.whamcloud.com/job/lustre-b1_8/100" class="external-link" target="_blank" rel="nofollow noopener">http://build.lab.whamcloud.com/job/lustre-b1_8/100</a>, which was Lustre 1.8.6-wc1. <a href="https://jira.whamcloud.com/browse/LU-544" title="1.8&lt;-&gt;2.1 interop: conf-sanity test 56: mkfs.lustre FAIL: Journal size too big for filesystem." class="issue-link" data-issue-key="LU-544"><del>LU-544</del></a> was fixed after that release.</p> <p>Since we always test the interop between the latest b1_8 release and 2.x release, could you please update the autotest system to use Lustre 1.8.7-wc1 release build <a href="http://newbuild.whamcloud.com/job/lustre-b1_8/150/" class="external-link" target="_blank" rel="nofollow noopener">http://newbuild.whamcloud.com/job/lustre-b1_8/150/</a> ? Thanks!</p> <p>This is believed to be fixed in 1.8.7. Please reopen if it reoccurs with 1.8.7</p> Development Rank 1|hzvbsv: Rank (Obsolete) 5476 Severity