[lustre-discuss] mount not possible: "no server support"

Andreas Dilger adilger at whamcloud.com
Thu Oct 19 05:47:19 PDT 2023



On Oct 19, 2023, at 19:58, Benedikt Alexander Braunger via lustre-discuss <lustre-discuss at lists.Lustre.org<mailto:lustre-discuss at lists.Lustre.org>> wrote:

Hi Lustrers,

I'm currently struggling with a unmountable Lustre filesystem. The client only says "no server support", no further logs on client or server.
I first thought this might be related to the usage of fscrypt but I already recreated the whole filesystem from scratch and the error still persists.
Now I have no more idea what to look for.

Here the full CLI log:

[root at dstorsec01vl]# uname -a
Linux dstorsec01vl 5.14.0-284.11.1.el9_2.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 12 10:45:03 EDT 2023 x86_64 x86_64 x86_64 GNU/Linux

[root at dstorsec01vl]# modprobe lnet
[root at dstorsec01vl]# modprobe lustre
[root at dstorsec01vl]# lnetctl ping pstormgs01 at tcp
ping:
    - primary nid: 10.106.104.160 at tcp
      Multi-Rail: False
      peer ni:
        - nid: 10.106.104.160 at tcp

[root at dstorsec01vl]# mount -t lustre pstormgs01 at tcp:sif0 /mnt/
mount.lustre: cannot mount pstormgs01 at tcp:sif0: no server support

It looks like this is failing because the mount device is missing ":/"  in it, which mount.lustre uses to decide whether this is a client or server mountpoint.  you should be using:

    client# mount -t lustre pstormgs01 at tcp:/sif0 /mnt/sif0

and this should work.  It probably makes sense to improve the error message to be more clear, like:

   mount.lustre: cannot mount block device 'pstormgs01 at tcp:sif0': no server support

or similar

Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Whamcloud







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20231019/a004ed3f/attachment.htm>


More information about the lustre-discuss mailing list