I figure out the problem was a wrong setting client side.
On 8/7/17 8:09 PM, Riccardo Veraldi wrote:
> it is like if my /etc/modprobe.d/lustre.conf gets completely ignored
> when lnet module is loaded
>
> On 8/7/17 7:05 PM, Cowe, Malcolm J wrote:
>> Lustre file system names cannot exceed 8 charact
it is like if my /etc/modprobe.d/lustre.conf gets completely ignored
when lnet module is loaded
On 8/7/17 7:05 PM, Cowe, Malcolm J wrote:
> Lustre file system names cannot exceed 8 characters in length, but
> “scratch12” is 9 characters. Try changing the fsname to a smaller string. You
> can do
thanks, yes I noticed that Issued and I changed hte name. I Also rebuild
the FS but now it does not work for another unknown reason:
Aug 7 19:05:38 psana1510 kernel: [289134.511260] Lustre:
:0:(client.c:2114:ptlrpc_expire_one_request()) @@@ Request sent has
failed due to network error: [sent
Lustre file system names cannot exceed 8 characters in length, but “scratch12”
is 9 characters. Try changing the fsname to a smaller string. You can do this
with tunefs.lustre on all the storage targets, but I can’t remember if you need
to use --erase-params and recreate all the options. Alterna
trying to debug more this problem looks like tcp port 9888 is closed on
the MDS.
this is weird. lnet module is running. There is no firewall and OSSs and
MDS are on the same subnet.
but I Cannot connect to port 9888.
There is anything which changed in Lustre 2.10.0 related to lnet and TCP
ports tha
Hello,
I have a new Lustre cluster based on Lustre 2.10.0/ZFS 0.7.0 on Centos 7.3
Lustre FS creation went smooth.
When I tryed then to mount from the clients, Lustre is not able to mount
any of the OSTs.
It stops at MGS/MDT level.
this is from the client side:
mount.lustre: mount 192.168..48.254
