[lustre-discuss] mount not possible: "no server support"
Benedikt Alexander Braunger
bebr at adm.ku.dk
Thu Oct 19 02:58:36 PDT 2023
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
[root at dstorsec01vl]# dmesg | tail
[ 90.582867] libcfs: loading out-of-tree module taints kernel.
[ 90.583149] libcfs: module verification failed: signature and/or
required key missing - tainting kernel
[ 90.586887] LNet: HW NUMA nodes: 1, HW CPU cores: 1, npartitions: 1
[ 90.591213] alg: No test for adler32 (adler32-zlib)
[ 91.341004] Key type ._llcrypt registered
[ 91.341009] Key type .llcrypt registered
[ 93.708911] Lustre: Lustre: Build Version: 2.15.3
[ 93.789571] LNet: Added LNI 10.106.104.166 at tcp [8/256/0/180]
[ 93.789629] LNet: Accept secure, port 988
Any help or ideas appreciated :-)
More information about the lustre-discuss
mailing list