[lustre-discuss] 2.10.1 client fails to mount on 2.9 backend

Chris Horn hornc at cray.com
Fri Nov 17 13:48:18 PST 2017


Is the MGS actually on tcp or is it on o2ib? Can you “lctl ping” the MGS LNet nid from the client where you’re trying to mount?

Chris Horn

From: lustre-discuss <lustre-discuss-bounces at lists.lustre.org> on behalf of Christopher Johnston <chjohnst at gmail.com>
Date: Friday, November 17, 2017 at 3:17 PM
To: lustre-discuss <lustre-discuss at lists.lustre.org>
Subject: [lustre-discuss] 2.10.1 client fails to mount on 2.9 backend

Just tested the new 2.10.1 client against one of my fileservers where I have 2.9 running.   Works with 2.10.0 but not 2.10.1, is this expected?

# mount -t lustre 172.30.69.90:/qstore /mnt
mount.lustre: mount 172.30.69.90:/qstore at /mnt failed: No such file or directory
Is the MGS specification correct?
Is the filesystem name correct?
If upgrading, is the copied client log valid? (see upgrade docs)

# dmesg -e | tail -4
[Nov17 16:15] LustreError: 22344:0:(ldlm_lib.c:483:client_obd_setup()) can't add initial connection
[  +0.009423] LustreError: 22344:0:(obd_config.c:608:class_setup()) setup MGC172.30.69.90 at tcp failed (-2)
[  +0.009755] LustreError: 22344:0:(obd_mount.c:203:lustre_start_simple()) MGC172.30.69.90 at tcp setup error -2
[  +0.010193] LustreError: 22344:0:(obd_mount.c:1505:lustre_fill_super()) Unable to mount  (-2)

-Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20171117/9c69c206/attachment-0001.html>


More information about the lustre-discuss mailing list