Whamcloud Community JIRA

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-2460] Failed to mount ost: Transport endpoint is not connected https://jira.whamcloud.com/browse/LU-2460 Lustre <p>This issue was created by maloo for sarah <sarah@whamcloud.com></p> <p>This issue relates to the following test suite run: <a href="https://maloo.whamcloud.com/test_sets/3b49fb7c-4241-11e2-adcf-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sets/3b49fb7c-4241-11e2-adcf-52540035b04c</a>.</p> <p>Transport endpoint is not connected</p> LU-2460

Failed to mount ost: Transport endpoint is not connected

Bug Blocker Resolved Fixed Chris Gearing Maloo LB Mon, 10 Dec 2012 16:38:36 +0000 Fri, 21 Dec 2012 13:33:47 +0000 Fri, 21 Dec 2012 13:33:47 +0000 Lustre 2.4.0 0 6 <p>I resubmitted the test and this error gone.<br/> <a href="https://maloo.whamcloud.com/test_sessions/94231f70-44a4-11e2-8c8b-52540035b04c" class="external-link" target="_blank" rel="nofollow noopener">https://maloo.whamcloud.com/test_sessions/94231f70-44a4-11e2-8c8b-52540035b04c</a></p> <p>Chris</p> <p>Any idea why this occurred?</p> <p>Peter</p> <p>Last entry from the maloo log files indicated that MDT on client-20 were created and mounted, <br/> but mounting of first created OST on client-21 failed. The error listed indicate an connection problem:</p> <p>— snip ----<br/> ...<br/> 11:41:20:Started lustre-MDT0000<br/> 11:41:20:CMD: client-21-ib mkdir -p /mnt/ost1<br/> 11:41:20:CMD: client-21-ib test -b /dev/lvm-OSS/P1<br/> 11:41:21:Starting ost1: /dev/lvm-OSS/P1 /mnt/ost1<br/> 11:41:21:CMD: client-21-ib mkdir -p /mnt/ost1; mount -t lustre /dev/lvm-OSS/P1 /mnt/ost1<br/> 11:41:42:client-21-ib: mount.lustre: mount /dev/mapper/lvm--OSS-P1 at /mnt/ost1 failed: Transport endpoint is not connected<br/> ...<br/> —<br/> This could indicate an IB problem, LNET or problem with missing module, but might be a problem with the storage backend.<br/> Unfortunatly the messsage files of the nodes client-</p> {20,21} <p> are gone since they have been re-installed by 12.12.<br/> I will check on Monday with Chis whether the message files can be recovered.</p> <p>The other track is the IB health.</p> <p>The opensmd might have been 'moved' client-6, this might be the reason:</p> <p>root 6727 1 11 Dec11 ? 06:49:20 /usr/sbin/opensm -B -F /etc/rdma/opensm.conf.<span class="error">[0-9]</span>*<br/> <span class="error">[root@client-6 ~]</span># uptime<br/> 09:39:51 up 2 days, 11:35, 1 user, load average: 2.01, 2.01, 1.98<br/> <span class="error">[root@client-6 ~]</span># date<br/> Fri Dec 14 09:39:55 PST 2012</p> <p>Therefore no opensm.log entries are available when the test were running (09.12.2012 ~ 11:40).<br/> At the moment I could see many part state changes for 2 switches, that could indicate some problems.<br/> I will contact Joshua </p> <p>Have to check this with Chris on Monday since I don't have access to some tools on mgmt and brent.<br/> I couldn't find the output of inspectdianet on client-6. Have to contact Joshua on Monday. I don't <br/> want to mess up something. <br/> This is another track for analysis...</p> <p>root FS <img class="emoticon" src="https://jira.whamcloud.com/images/icons/emoticons/check.png" height="16" width="16" align="absmiddle" alt="" border="0"/> ran full on client-6. Reason is most likely VM feature enable for HCA on client-9<br/> opensmd isn't capable of handling VM request --> leads to tons of error message of the form:</p> <p>Dec 11 22:12:45 701384 <span class="error">[5A875700]</span> 0x01 -> osm_gir_rcv_process: ERR 5105: Unsupported Method (SubnAdmSet).</p> <p>opensm.log size:<br/> <span class="error">[root@client-6 log]</span># ll opensm.log <br/> <del>rw-r</del><del>r</del>- 1 root root 19136745472 Dec 14 11:51 opensm.log</p> <p>Saved copy of opensm.log to /home/frank/logs and stopped HCA on client-9 and cleaned up logfile. </p> <p>subnet manager operational. ping test of ib-interface were successfull, before and after the cleanup.</p> <p>Resolved by restarting opensm and we have a ticket in place (TT-992) to properly resolve the opensm issue. </p> Development Rank 1|hzvdkf: Rank (Obsolete) 5804 Severity