Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 2.4.0
-
None
-
3
-
4333
Description
The patch from review 4068 seems to use the wrong uuid for MDT0000, causing error messages like this:
LustreError: 137-5: UUID 'lustre-MDT0000-MDT0000_UUID' is not available for connect (no target) LustreError: 11-0: an error occurred while communicating with 0@lo. The mds_connect operation failed with -19 [root@fat-amd-1 tests]# cat /proc/fs/lustre/osp/*/ost_server_uuid lustre-MDT0000-MDT0000_UUID DISCONN lustre-MDT0000-MDT0000_UUID DISCONN lustre-MDT0000-MDT0000_UUID DISCONN lustre-OST0000_UUID FULL lustre-OST0001_UUID FULL
Somehow, we end up with MDT0000 twice in the UUID. This is harmless for now because nobody uses this connection, but this should be fixed ASAP.
I talked to wangdi and he said that he is going to look into this issue.