Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
None
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for Marc Vef <mvef@whamcloud.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/a09882d9-8aa5-4ac7-93de-c8ed85f700b2
lustre-initialization failed with the following error:
"lustre-initialization timed out"
Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/123839 - 5.14.0-503.40.1.el9_5.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/123839 - 5.14.0-503.40.1_lustre.el9.x86_64
from dmesg
[Mon Apr 13 13:59:10 2026] Lustre: DEBUG MARKER: /usr/sbin/lnetctl lnet configure -a -l [Mon Apr 13 14:00:42 2026] Lustre: DEBUG MARKER: mkdir -p /mnt/lustre [Mon Apr 13 14:00:42 2026] Lustre: DEBUG MARKER: mount -t lustre -o user_xattr,flock fd33:3981:3213:f020:0:5254:55:98bd@tcp:/lustre /mnt/lustre [Mon Apr 13 14:00:43 2026] LustreError: 13942:0:(mgc_request.c:1478:mgc_apply_recover_logs()) mgc: cannot find UUID by nid 'fd33:3981:3213:f020:0:5254:6b:2911@tcp': rc = -2 [Mon Apr 13 14:00:43 2026] Lustre: 13942:0:(mgc_request.c:1647:mgc_process_recover_log()) MGCfd33:3981:3213:f020:0:5254:55:98bd@tcp: error processing lustre-cliir log recovery: rc = -2 [Mon Apr 13 14:00:43 2026] Lustre: 13942:0:(mgc_request.c:1917:mgc_process_log()) MGCfd33:3981:3213:f020:0:5254:55:98bd@tcp: IR log lustre-cliir failed, not fatal: rc = -2 [Mon Apr 13 14:01:03 2026] LustreError: lustre-MDT0002-mdc-ff3a6e9942e3a000: operation mds_connect to node fd33:3981:3213:f020:0:5254:55:98bd@tcp failed: rc = -11 [Mon Apr 13 14:01:33 2026] LustreError: lustre-MDT0000-mdc-ff3a6e9942e3a000: operation mds_connect to node fd33:3981:3213:f020:0:5254:55:98bd@tcp failed: rc = -11
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
lustre-initialization lustre-initialization - "lustre-initialization timed out"
Attachments
Issue Links
- duplicates
-
LU-18041 struct obd_uuid is too small for MGC"NID" uuid with IPv6
-
- Open
-