Not sure if it's your case but the order of MGS' NIDs when mounting matters:
[root@my-ms-01xx-yy ~]# time mount -t lustre 10.210.1.101@tcp:10.210.1.102@tcp:/fs2 /scratch real 0m0.215s user 0m0.007s sys 0m0.059s [root@my-ms-01xx-yy ~]# time mount -t lustre 10.210.1.102@tcp:10.210.1.101@tcp:/fs2 /scratch real 0m25.196s user 0m0.009s sys 0m0.033s Since the MGS is running on the node having the IP "10.210.1.101", if we first try with the other one there seems to be a timeout of 25s. Diego On 03.02.20, 23:17, "lustre-discuss on behalf of Andrew Elwell" <[email protected] on behalf of [email protected]> wrote: Hi Folks, One of our (recently built) 2.10.x filesystems is slow to mount on clients (~20 seconds) whereas the others are nigh on instantaneous. We saw this before with a 2.7 filesystem that went away after doing <something unknown / filesystem upgrade> but we've no idea what. Nothing obvious in the logs. Does anyone have suggestions for what causes this, and how to make it faster? It's annoying me as "something" isn't right but I can't identify what. Many thanks Andrew _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
