Re: [lustre-discuss] Strange lustre 2.7 client behavior

I have downgraded machines causing the issue to 2.7.0.1 client It doesn't have the folder issue, but in 2.7.65 : The ls -l command issued in a script by the nrpe agent cause the "lustre-MDT-mdc-88032e4cb000: operation ldlm_enqueue to node 10.0.1.60@tcp failed: rc = -14" error in the

Re: [lustre-discuss] Strange lustre 2.7 client behavior

Ok then No backward compatibility issue with our 2.6 servers ? I can downgrade to 2.7 if it is better Thanks Le 25/04/2016 20:47, Dilger, Andreas a écrit : I wouldn't recommend to run 2.7.65 now that 2.8.0 is released. That is a development version and suitable for testing, but a lot of

Re: [lustre-discuss] Strange lustre 2.7 client behavior

I wouldn't recommend to run 2.7.65 now that 2.8.0 is released. That is a development version and suitable for testing, but a lot of fixes have been landed into the 2.8.0 release. Cheers, Andreas > On Apr 25, 2016, at 09:46, Jérôme BECOT wrote: > > Hi, > > This is

Re: [lustre-discuss] Strange lustre 2.7 client behavior

Le 25/04/2016 17:46, Jérôme BECOT a écrit : Hi, This is not really an issue, but I wondered if you already got it : Fresh installed linux machines. Lustre client 2.7.65 recompiled for kernel 3.10.0-327.10.1.el7.x86_64 on CentOS 7.2 I boot the machine. "/scratch" folder is mounted from

[lustre-discuss] Strange lustre 2.7 client behavior

Hi, This is not really an issue, but I wondered if you already got it : Fresh installed linux machines. Lustre client 2.7.65 recompiled for kernel 3.10.0-327.10.1.el7.x86_64 on CentOS 7.2 I boot the machine. "/scratch" folder is mounted from lustre with fstab I have an nagios nrpe daemon