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-6660 Lustre <p>This test is to verify 2.5/2.7 clients can work with DNE2 servers. <br/> For DNE2 server, it can use this build<br/> <a href="https://build.hpdd.intel.com/job/lustre-reviews/32529/" class="external-link" target="_blank" rel="nofollow noopener">https://build.hpdd.intel.com/job/lustre-reviews/32529/</a></p> <p>2.5/2.7 client can use the most update rpm in the build.<br/> <a href="https://build.hpdd.intel.com" class="external-link" target="_blank" rel="nofollow noopener">https://build.hpdd.intel.com</a></p> <p>Right now, we can check these two things.</p> <p>1. Sanity should pass as other inter-op test. <br/> 2. check if "lfs mkdir" and "lfs mv" works in this environment.</p> LU-6660

interop DNE2 test between 2.5/2.7 clients and DNE2 servers

Task Blocker Resolved Fixed Lai Siyao Di Wang Thu, 28 May 2015 16:43:25 +0000 Mon, 31 Aug 2015 16:02:12 +0000 Mon, 31 Aug 2015 16:02:12 +0000 Lustre 2.8.0 0 9 <p>It would be best to run this as much as possible via Test-Parameters: in Gerrit and alwaysuploadlogs so we get a good record of the tests run. </p> <p>Lai Siyao (lai.siyao@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/15099" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/15099</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6660" title="interop DNE2 test between 2.5/2.7 clients and DNE2 servers" class="issue-link" data-issue-key="LU-6660"><del>LU-6660</del></a> dne: interop with 2.5 clients<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 76c6df4f81b312145f1db674d89abc8a30e0281a</p> <p>Hi Lai;</p> <p>It looks like Autotest is failing early currently. Can you confirm that this test runs successfully on your local machine?</p> <p>Richard, it failed because 2.5 on el6.6 client is not supported by autotest, I've changed to b2_5_fe according to Yujian's advice.</p> <p>Local test result looks good so far, and I'll have autotest run also the make the result more clear. </p> <p><a href="https://testing.hpdd.intel.com/test_sets/bd8ddb6c-0e27-11e5-a0ac-5254006e85c2" class="external-link" target="_blank" rel="nofollow noopener">https://testing.hpdd.intel.com/test_sets/bd8ddb6c-0e27-11e5-a0ac-5254006e85c2</a> sanity test failures 24b, 24f, 24x and 27z look to be because DNE2 rename changed semantic, so for striped directory 2.7 client will fail with -EREMOTE, this should not be an issue since this is striped directory. 103b failure looks to be a real issue, and I have reproduced it locally, it looks to be there is an inflight OSP RPC, so OSP device refcount is not NULL upon umount, I'll continue investigating into it.</p> <p>As for 2.5 a wrong build number is specified in Test-parameters, I'll retrigger auto test.</p> <p>I'm not sure I understand about 2.7 clients and -EREMOTE? 2.7 clients DO support striped directories, but renames across stripes should return -EXDEV so that user space tools can handle this properly. If the Async commit causes clients to return -EREMOTE to applications then "mv" and other tools will fail. </p> <p>Indeed, this was introduced by <a href="http://review.whamcloud.com/#/c/12282/47" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/12282/47</a> for <a href="https://jira.whamcloud.com/browse/LU-3537" title="allow cross-MDT for all metadata operations " class="issue-link" data-issue-key="LU-3537"><del>LU-3537</del></a>, which adds support for cross-MDT rename, so once cross-MDT detected, DNE2 MDS return -EREMOTE, and LMV will retry with correct MDS. I'll add interop code to address this issue.</p> <p>Lai Siyao (lai.siyao@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/15323" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/15323</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6660" title="interop DNE2 test between 2.5/2.7 clients and DNE2 servers" class="issue-link" data-issue-key="LU-6660"><del>LU-6660</del></a> rename: DNE2 should return -EXDEV upon remote rename<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: b08334081bbfb07958cc51ceda785c1bff784252</p> <p>2.5 client failed tests:<br/> 132: failed because SOM is removed from master.<br/> 151,156: failed because lproc stats format changed, after I changed to use DNE2 format, tests can pass.<br/> 154a: failed because of <a href="https://jira.whamcloud.com/browse/LU-5424" title="Test failuresanity test_154b: create lov data thru .lustre should fail" class="issue-link" data-issue-key="LU-5424"><del>LU-5424</del></a>, which is not in 2.5, and 2.7 test script adds version check.</p> <p>2.7 client failed tests:<br/> 132: failed because SOM is removed from master.</p> <p>Lai, to confirm - the test failures in your last comment are when runnin with patch 15323 applied, and without that patch there are more failures due to -EREMOTE being returned to the client?</p> <p>It might be useful to submit patches to b2_5_fe and b2_7_fe to skip the SOM test 132. </p> <p>yes, Andreas.</p> <p>I'll do it later.</p> <p>Lai,</p> <p>Can this ticket be closed?</p> <p>Richard, you may wait for some time, cause when all patches landed, I'd like to test again to verify.</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/15323/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/15323/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6660" title="interop DNE2 test between 2.5/2.7 clients and DNE2 servers" class="issue-link" data-issue-key="LU-6660"><del>LU-6660</del></a> rename: DNE2 should return -EXDEV upon remote rename<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 31234e608fa156761b2d8c48ff60cba875dd4832</p> <p>Lai - Have you had a chance to to verify now that the patch has landed?</p> <p>Don't we need to back port it to 2.7 and 2.5?</p> <p>Hi James,</p> <p>Lustre 2.7 and 2.5 do not contain the patch <a href="http://review.whamcloud.com/12282" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/12282</a> for <a href="https://jira.whamcloud.com/browse/LU-3537" title="allow cross-MDT for all metadata operations " class="issue-link" data-issue-key="LU-3537"><del>LU-3537</del></a>, which introduced the issue. So, we do not need back-port <a href="http://review.whamcloud.com/15323" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/15323</a>.</p> <p>Di or Lai, could you please confirm on this?</p> <p>Jian, yes, you're right.</p> <p>Fix was landed for 2.8</p> Blocker LU-6858 Related LU-3531 Development Rank 1|hzxefr: Rank (Obsolete) 9223372036854775807