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-5076 Lustre <p>This issue was created by maloo for wangdi &lt;di.wang@intel.com&gt;</p> <p>This issue relates to the following test suite run: <a href="http://maloo.whamcloud.com/test_sets/0638f47c-dd56-11e3-8e9b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">http://maloo.whamcloud.com/test_sets/0638f47c-dd56-11e3-8e9b-52540035b04c</a>.</p> <p>The sub-test test_46a failed with the following error:</p> <blockquote> <p>Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000240000400-0x0000000280000400):1:ost<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 3 previous similar messages<br/> Lustre: ctl-lustre-MDT0000: super-sequence allocation rc = 0 [0x0000000300000400-0x0000000340000400):4:ost<br/> Lustre: Skipped 2 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 6 previous similar messages<br/> Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0000_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc26b. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086d9c<br/> Lustre: Skipped 62 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 12 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 24 previous similar messages<br/> LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.<br/> LustreError: Skipped 94 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 50 previous similar messages<br/> Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0001_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc33d. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086f01<br/> Lustre: Skipped 306 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 102 previous similar messages<br/> LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.<br/> LustreError: Skipped 120 previous similar messages<br/> Lustre: lustre-MDT0000: already connected client lustre-MDT0000-lwp-OST0000_UUID (at 10.10.4.199@tcp) with handle 0x2fb538c53b7cc26b. Rejecting client with the same UUID trying to reconnect with handle 0x4f578b0725086d9c<br/> Lustre: Skipped 364 previous similar messages<br/> Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected<br/> Lustre: Skipped 120 previous similar messages<br/> LustreError: 11-0: lustre-OST0006-osc-MDT0000: Communicating with 10.10.4.199@tcp, operation ost_connect failed with -11.<br/> test failed to respond and timed out</p></blockquote> <p>This failure is a bit strange, according to the syslog on MDS0</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: lustre-MDT0000: Client lustre-MDT0000-lwp-OST0006_UUID seen on new nid 10.10.4.199@tcp when existing nid 10.10.4.203@tcp is already connected </pre> </div></div> <p>But the ip of OSS should be on 10.10.4.199, I do not know where this 10.10.4.203 comes from. So I am not sure this is a TEI ticket. If some one confirm this is a TEI ticket, please close this one. Thanks.</p> <p>Info required for matching: conf-sanity 46a</p> LU-5076

Test failure on test suite conf-sanity, subtest test_46a test failed to respond and timed out

Bug Minor Resolved Duplicate Minh Diep Maloo Sat, 17 May 2014 01:20:59 +0000 Tue, 10 Jun 2014 17:07:21 +0000 Tue, 10 Jun 2014 17:07:21 +0000 0 4 <p>It would we worthwhile to track down which mv cluster this other IO address belongs to, and why it thinks it should be connecting to this MDS. </p> <p>Separately, one option to avoid such problems is to use a more unique $NAME variable for each test cluster (e.g. hostname of master test node instead of ALWAYS "lustre") so that the clients and servers are not able to connect to the wrong system being tested. </p> <p>Closing this as a duplicate of TEI-1993. There are two possible fixes in the test infrastructure that are possible:</p> <ul class="alternate" type="square"> <li>fix the test system not to leave test nodes running after changing the cluster config</li> <li>fix the test system to assign more unique filesystem names for tests, so that old servers do not think they should be connecting to new servers</li> </ul> Duplicate Related LU-5064 Development Rank 1|hzwmon: Rank (Obsolete) 14010 Severity