Thanks for the feedback, Riccardo.  I understand not all versions are certified 
compatible but knowing that some folks have had success helps build some 
confidence.  I tried building 2.8.0, the latest from the 2.8 branch, the latest 
from the 2.9 branch, 2.10.2, and the latest from master 
(2.10.56_85_g76afb10-1). Only the latter two succeeded.


I'll run some tests and hold off to see if other chime in with known successes 
or known issues.  I'm ldiskfs, not zfs.  Tcp only, not infiniband or RDMA.  No 
lnet routers. Independent MGT and MDT, rather than combined.  48 OSTs and about 
70 clients.  Pretty basic config.  Fingers crossed on more similar success 
stories.


Cheers,

Scott

________________________________
From: Riccardo Veraldi <riccardo.vera...@cnaf.infn.it>
Sent: Monday, 8 January 2018 5:28:42 PM
To: Scott Wood; lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] Issues compiling lustre-client 2.8 on CentOS 7.4

I am running at the moment 2.10.1 clients with any server version down to 2.5 
without troubles. I know that there is no warranty of full interoperability bot 
so far I did not have problems.
Not sure if you can run 2.8 on Centos 7.4. You can try to git clone the latest 
source code from 2.8.* and see if it builds on Centos 7.4

On 1/7/18 8:10 PM, Scott Wood wrote:

Afternoon, folks,


In the interest of patching kernels to mitigate Meltdown security issues on 
user accessible systems, we're trying to build lustre client rpms for the 
latest released Centos 7.4 kernel, 3.10.0-693.11.6.el7.x86_64.  We're running 
in to issues compiling though.  As I understand from the docs, as our servers 
are CentOS6 and running the Intel distributed 2.7.0 server binaries, the newest 
"officially" supported client versions are lustre 2.8.


Has anyone run the 2.10.2 (or 2.10.x) clients connecting to 2.7.0 servers (as 
we have successfully built all client rpms from a current git checkout, and 
from a 2.10.2 checkout)?  Alternatively, is there a known 2.8.x tag that builds 
successfully on CentOS7.4?  Is there a third option that folks would propose?


build errors visible at https://pastebin.com/izF3bXg3


Cheers

Scott



_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org


_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Reply via email to