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-3152 Lustre <p>= sanity test 27z: check SEQ/OID on the MDT and OST filesystems == 11:25:05 (1365618305)<br/> 1+0 records in<br/> 1+0 records out<br/> 1048576 bytes (1.0 MB) copied, 0.0425101 s, 24.7 MB/s<br/> 8+0 records in<br/> 8+0 records out<br/> 8388608 bytes (8.4 MB) copied, 0.317879 s, 26.4 MB/s<br/> check file /mnt/lustre/d0.sanity/d27/f.sanity.27z-1<br/> FID seq 0x4c0000400, oid 0x7aa ver 0x0<br/> LOV seq 0x4c0000400, oid 0x7aa, count: 1<br/> want: stripe:0 ost:0 oid:332/0x14c seq:0x200000400<br/> Stopping /mnt/ost1 (opts<img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/smile.png" height="16" width="16" align="absmiddle" alt="" border="0"/> on oss01<br/> oss01: find: `/mnt/ost1/O/0x200000400': No such file or directory<br/> Starting ost1: /dev/disk/by-id/scsi-3600d0231000d0143506404614c0b55f4-part1 /mnt/ost1<br/> Started lustre-OST0000<br/> sanity test_27z: @@@@@@ FAIL: : no filter_fid info<br/> Trace dump:<br/> = /usr/lib64/lustre/tests/test-framework.sh:4022:error_noexit()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4045:error()<br/> = /usr/lib64/lustre/tests/sanity.sh:1745:check_seq_oid()<br/> = /usr/lib64/lustre/tests/sanity.sh:1789:test_27z()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4284:run_one()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4317:run_one_logged()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4187:run_test()<br/> = /usr/lib64/lustre/tests/sanity.sh:1792:main()<br/> Dumping lctl log to /tmp/test_logs/2013-04-10/104917/sanity.test_27z.*.1365618315.log<br/> c21: Host key verification failed.^M<br/> c21: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> c21: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> c13: Host key verification failed.^M<br/> c13: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> c13: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> c15: Host key verification failed.^M<br/> c15: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> c15: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> c14: Host key verification failed.^M<br/> c14: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> c14: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> c22: Host key verification failed.^M<br/> c22: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> c22: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> mds03: Host key verification failed.^M<br/> mds03: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> mds03: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> oss02: Host key verification failed.^M<br/> oss02: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> oss02: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> mds02: Host key verification failed.^M<br/> mds02: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> mds02: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> oss01: Host key verification failed.^M<br/> oss01: rsync: connection unexpectedly closed (0 bytes received so far) <span class="error">&#91;sender&#93;</span><br/> oss01: rsync error: unexplained error (code 255) at io.c(600) <span class="error">&#91;sender=3.0.6&#93;</span><br/> sanity test_27z: @@@@@@ FAIL: test_27z failed with 5<br/> Trace dump:<br/> = /usr/lib64/lustre/tests/test-framework.sh:4022:error_noexit()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4045:error()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4284:run_one()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4317:run_one_logged()<br/> = /usr/lib64/lustre/tests/test-framework.sh:4187:run_test()<br/> = /usr/lib64/lustre/tests/sanity.sh:1792:main()<br/> Dumping lctl log to /tmp/test_logs/2013-04-10/104917/sanity.test_27z.*.1365618328.log</p> LU-3152

test_27z did not consider fid on OST.

Bug Blocker Resolved Fixed Di Wang Di Wang LB Wed, 10 Apr 2013 22:26:20 +0000 Fri, 19 Apr 2013 12:18:22 +0000 Fri, 19 Apr 2013 12:18:22 +0000 Lustre 2.4.0 Lustre 2.4.0 0 5 <p>I have a fix in <a href="http://review.whamcloud.com/5785" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/5785</a> that removes the "0x" prefix of the sequence number.</p> <p>so how serious is this? only when we run in fid on ost mode (is that like just for DNE?) I don't think we ever hit this in our regular testing yet?</p> <p>There is also a separate issue for the output of "lfs getstripe -v" which prints lmm_object_id and lmm_seq (formerly called lmm_object_gr) for a file that was created with 2.1-2.3.56 versions of Lustre. The 1.8 and current master branches use this consistently, where lmm_oi.oi_fid.f_seq is the sequence (IGIF seq == inode in the 1.8 case).</p> <p>I submitted <a href="http://review.whamcloud.com/6026" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6026</a> to fix that, which should also be ported to b2_1 in case someone is using old clients with 2.4 servers. The lmm_oi will be repaired by LFSCK Phase 2 so that its usage is consistent.</p> <p>Per issues in <a href="https://jira.whamcloud.com/browse/LU-2888" title="After downgrade from 2.4 to 2.1.4, hit (osd_handler.c:2343:osd_index_try()) ASSERTION( dt_object_exists(dt) ) failed" class="issue-link" data-issue-key="LU-2888"><del>LU-2888</del></a> I'm bumping this to be an HB, since the on-disk format for the LLOG files was accidentally changed, but missed during upgrade testing. Di is working on a patch to fix that, which should be included in the next tag instead of afterward.</p> <p>My patch in <a href="http://review.whamcloud.com/6026" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6026</a> will not be needed at all if Di's patch in <a href="http://review.whamcloud.com/6037" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/6037</a> lands.</p> <p>Andreas</p> <p>The latter patch has been abandoned but I now see <a href="http://review.whamcloud.com/#change,6022" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#change,6022</a> for this issue - should that land?</p> <p>Peter</p> <p>Landed for 2.4</p> Development Rank 1|hzvnmf: Rank (Obsolete) 7642 Severity