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-999 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://maloo.whamcloud.com/test_sets/cbcbbd2e-3f50-11e1-990e-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/cbcbbd2e-3f50-11e1-990e-5254004bbbd3</a>.</p> <p>fat-intel-1vm4: error getting mds_hdr (3685469441:8) in /tmp/mdsdb: DB_NOTFOUND: No matching key/data pair found<br/> fat-intel-1vm4: e2fsck: aborted<br/> Pass 1: Checking inodes, blocks, and sizes<br/> Pass 1: Memory used: 432k/0k (265k/168k), time: 0.07/ 0.01/ 0.02<br/> Pass 1: I/O read: 7MB, write: 0MB, rate: 100.18MB/s<br/> Pass 2: Checking directory structure<br/> Pass 2: Memory used: 432k/0k (291k/142k), time: 0.00/ 0.00/ 0.00<br/> Pass 2: I/O read: 3MB, write: 0MB, rate: 1337.49MB/s<br/> Pass 3: Checking directory connectivity<br/> Peak memory: Memory used: 432k/0k (308k/125k), time: 0.11/ 0.01/ 0.03<br/> Pass 3: Memory used: 432k/0k (291k/142k), time: 0.00/ 0.00/ 0.00<br/> Pass 3: I/O read: 1MB, write: 0MB, rate: 27027.03MB/s<br/> Pass 4: Checking reference counts<br/> Pass 4: Memory used: 396k/0k (164k/233k), time: 0.00/ 0.00/ 0.00<br/> Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s<br/> Pass 5: Checking group summary information<br/> Pass 5: Memory used: 396k/0k (148k/249k), time: 0.02/ 0.01/ 0.00<br/> Pass 5: I/O read: 1MB, write: 0MB, rate: 64.42MB/s<br/> Pass 6: Acquiring OST information for lfsck<br/> lfsck : @@@@@@ FAIL: e2fsck <del>d -v -t -t -f -n --mdsdb /tmp/mdsdb --ostdb /tmp/ostdb-0 /dev/mapper/lvm</del>-OSS-P0 returned 8, should be &lt;= 1 </p> LU-999

Test failure on test suite lfsck

Bug Blocker Resolved Duplicate Zhenyu Xu Maloo Mon, 16 Jan 2012 13:34:59 +0000 Mon, 6 Feb 2012 21:45:49 +0000 Mon, 6 Feb 2012 21:45:28 +0000 Lustre 2.2.0 0 5 <p>Bobi</p> <p>Could you please look into this one?</p> <p>Thanks</p> <p>Peter</p> <p>The first thing to check is if the same version of e2fsprogs is installed on the MDS and OSS? Next, check if the version of db4 used by e2fsck is the same on both. This bug was hit in the past, and was due to db4 version mismatches. Please search bugzilla for this error messages. </p> <p>error msg is:</p> <p>fat-intel-1vm4: error getting mds_hdr (3685469441:8) in /tmp/mdsdb: DB_NOTFOUND: No matching key/data pair found</p> <p>the corresponding e2fsck code are:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> memset(&amp;mds_hdr, 0, sizeof(mds_hdr)); mds_hdr.mds_magic = MDS_MAGIC; // ====&gt; 0xDBABCD01 == 3685469441 memset(&amp;key, 0, sizeof(key)); memset(&amp;data, 0, sizeof(data)); key.data = &amp;mds_hdr.mds_magic; key.size = sizeof(mds_hdr.mds_magic); data.data = &amp;mds_hdr; data.size = sizeof(mds_hdr); data.ulen = sizeof(mds_hdr); data.flags = DB_DBT_USERMEM; rc = mds_hdrdb-&gt;get(mds_hdrdb, NULL, &amp;key, &amp;data, 0); if (rc) { fprintf(stderr,"error getting mds_hdr ("LPU64":%u) in %s: %s\n", mds_hdr.mds_magic, (int)sizeof(mds_hdr.mds_magic), ctx-&gt;lustre_mdsdb, db_strerror(rc)); ctx-&gt;flags |= E2F_FLAG_ABORT; goto out; } </pre> </div></div> <p>e2fsck cannot find the correct mds header magic value in /tmp/mdsdb when generating ost db.</p> <p>This could be caused by db4 version mismatch, but I checked the test session info <a href="https://maloo.whamcloud.com/test_sessions/99aea334-3f4f-11e1-990e-5254004bbbd3" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/99aea334-3f4f-11e1-990e-5254004bbbd3</a>, MDS(fat-intel-1vm3) and OSTs(fat-intel-1vm4) use the same build image (Kernel Version: 2.6.32-131.17.1.el6_lustre.ge126ace.x86_64 Lustre Version: jenkins-arch=x86_64,build_type=server,distro=el6,ib_stack=inkern)</p> <p>Is the /tmp/mdsdb file available on the OSS node, and is it definitely the right one (i.e. not left over from some previous run)? I haven't checked this code to verify if it will fail with a "file not found" if the mdsdb file is missing entirely. Since the OSS and MDS are running in different VM images, it may be that the file is not being copied to the OSS correctly.</p> <p>Sarah,</p> <p>Would you please check whether /tmp is a shared directory among MDS and OSS, and whether /tmp/mdsdb on the OSS node is exactly the same one as on the MDS node if we got another hit?</p> <p>Thanks.</p> <p>It seems this is the same issue as <a href="https://jira.whamcloud.com/browse/LU-427" title="Test failure on test suite lfsck" class="issue-link" data-issue-key="LU-427"><del>LU-427</del></a>.</p> <p>yes, I think it's dup of <a href="https://jira.whamcloud.com/browse/LU-427" title="Test failure on test suite lfsck" class="issue-link" data-issue-key="LU-427"><del>LU-427</del></a>, thanks Yujian.</p> Duplicate LU-427 Development Rank 1|hzvhi7: Rank (Obsolete) 6485 Severity