12:59 p.m.
If you have clients running 2.6.90+ but the servers are running 2.6.0 then at least none
of the in-development features from 2.6.90+ that might affect performance would be in
use.
If this is working for you, then I would suggest to stick with this version on your
production systems until after 2.7.0 is released. Of course, if you are willing to test
the development releases that is fine too, but I don't recommend that for any
filesystems containing important data.
The 2.6.0 release is not going to get maintenance updates. There is no plan yet which
future release will get a maintenance branch. It would likely be either 2.7 or 2.8.
Cheers, Andreas
On Jan 7, 2015, at 07:13, Jérôme BECOT <jerome.becot(a)inserm.fr>
wrote:
Well,
Because it's a fresh Lustre install and we decided to run our tests on the 2.6
version. We are quite satisfied and we plan to turn in production next month. As the 2.7
is comming soon I believed that the 2.6 will become the next maintenance release, but I
may be wrong ?
This is why I asked this : the servers are 2.6.0 and running well since the clients are
> 2.6.90
If I am wrong maybe we shall consider to downgrade to 2.5 ? But would it be a problem as
the clients are CentOS 7 ? We picked up the already availables rpms at Jenkins for
convenience, as the CentOS 7 and 3.10 Kernel versions are there.
Le 07/01/2015 14:04, Dilger, Andreas a écrit :
> The 2.6.91 tag is for a pre-release version of Lustre. That means that it is still
possible there are major bugs, protocol changes, and other fixes to be made before
release. As Patrick points out, there is at least one serious bug that prevents
downgrading once you've upgraded, which might be necessary if you hit other bugs.
>
> I would only recommend using 2.6.9x for testing at this point, and not for production
releases.
>
> What is the reason you want to upgrade to a development tag instead of sticking on a
maintenance branch?
>
> Cheers, Andreas
> --
> Andreas Dilger
> Lustre Software Architect
> Intel High Performance Data Division
>
> On 2015/01/06, 9:00 AM, "Patrick Farrell"
<paf@cray.com<mailto:paf@cray.com>> wrote:
>
> Upgrading should be OK, but it is not currently possible to downgrade to 2.6 (or
earlier versions). See LU-6050 for details: https://jira.hpdd.intel.com/browse/LU-6050
>
> Depending on what you do while the system is upgraded, you may be able to downgrade,
but any files created while 2.6.90 was running will have permissions issues, and it's
possible to get in a situation where you can't write to the file system after
downgrade.
>
> - Patrick
>
> On 01/06/2015 03:17 AM, Jérôme BECOT wrote:
> Hello,
>
> Can someone here confirm if i'm safe from any risk of data corruption or any
further troubles by upgrading my MDS and OSS servers software from the online feature
release 2.6.0-RC2--PRISTINE-2.6.32-431.20.3.el6_lustre.x86_64 to the last 2.6.91 version ?
or is there some modifications that may lead to a possible crash ?
>
> (proceeding to the usual stop-start services respecting the good order)
>
> We are running test over our new platform here that lasts for more consequent
purposes and as the 2.7 will be out there shortly we want to keep it functionnal in 2.6.
>
> Thanks
--
Jérome BECOT
Administrateur Systèmes et Réseaux
Molécules à visée Thérapeutique par des approches in Silico (MTi)
Univ Paris Diderot, UMRS973 Inserm
Case 013
Bât. Lamarck A, porte 412
35, rue Hélène Brion 75205 Paris Cedex 13
France
Tel : 01 57 27 83 82