On Oct 19, 2023, at 19:58, Benedikt Alexander Braunger via lustre-discuss <lustre-discuss@lists.Lustre.org<mailto:lustre-discuss@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@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@dstorsec01vl]# modprobe lnet [root@dstorsec01vl]# modprobe lustre [root@dstorsec01vl]# lnetctl ping pstormgs01@tcp ping: - primary nid: 10.106.104.160@tcp Multi-Rail: False peer ni: - nid: 10.106.104.160@tcp [root@dstorsec01vl]# mount -t lustre pstormgs01@tcp:sif0 /mnt/ mount.lustre: cannot mount pstormgs01@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@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@tcp:sif0': no server support or similar Cheers, Andreas -- Andreas Dilger Lustre Principal Architect Whamcloud
_______________________________________________ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org