[LU-7654] Lustre2.4.3 mgs/mdt mount error Created: 12/Jan/16  Updated: 19/Jan/16

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.3
Fix Version/s: None

Type: Question/Request Priority: Major
Reporter: Kaiming Ouyang Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Centos6.4


Epic/Theme: lustre, mgs, mount
Rank (Obsolete): 9223372036854775807

 Description   

Hello,
I am a beginner of Lustre.
I meet a very strange problem when I mount combined mgs/mdt file system.
Actually, I have installed all required software before I executed the following commands.
I firstly execute:
mkfs.lustre --fsname=temp --mgs --mdt --index=0 /dev/sdb

and then execute:
mount -t lustre /dev/sdb /mnt/mdt

But I got the error message:
LustreError:11-0: temp-MDT0000-lwp-MDT0000:Communicating with 0@lo, operation mds_connect failed with -11

I have examined all network connection, the connection works find. I don't know why I get this error. Can anyone give a suggestion? Thank you.



 Comments   
Comment by Andreas Dilger [ 12/Jan/16 ]

Did you check for errors on the console (demagogue)? This is typically caused by problems with host name resolution (e.g. host name maps to local host in /etc/hosts) or firewall rules that prevent connection on port 988.

Comment by Andreas Dilger [ 12/Jan/16 ]

Also, you need at least one OST mounted for the filesystem to be useful.

Comment by Malcolm Cowe (Inactive) [ 19/Jan/16 ]

Do the mount or df commands show the MDT as mounted? If so, this error can be ignored, I think, as a side-effect of not having any OSTs connected to the file system. For first time mounts, you have to mount the MGT and MDTs before the OSTs, but you get this side-effect.

Comment by Kaiming Ouyang [ 19/Jan/16 ]

No, MDT can't be mounted. I have mounted MGT and MDT before OST but it still has the same problem. Now, I found maybe it is a software bug, because I change it into Lustre2.7.0 and it works well. Thank you for your help!

Generated at Sat Feb 10 02:10:47 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.