[LU-1439] Compatibility between client version 2.1 & 2.2 and server version 1.8.4 (1.8.X) Created: 25/May/12  Updated: 01/Jun/12  Resolved: 01/Jun/12

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 1.8.x (1.8.0 - 1.8.5)
Fix Version/s: None

Type: Task Priority: Minor
Reporter: Nicola Bianchi Assignee: Peter Jones
Resolution: Fixed Votes: 0
Labels: None
Environment:
  • lustre servers version 1.8.4
  • lustre clients versions 2.1 & 2.2

Rank (Obsolete): 10147

 Description   

We are wondering which kind of compatibility we can expect between clients versions 2.1 & 2.2 and a server running the 1.8.4 version.
Do we have to expect stability problems?



 Comments   
Comment by Peter Jones [ 25/May/12 ]

Nicola

This would not be expected to work - 2.x clients are not supported for 1.8.x servers. This is due to a decision made during the 2.0 development cycle and so, while I cannot say for certain what the behaviour will be as we have never tested this, I think that it is safe to say that things will likely to work smoothly. Even for the converse, 2.x servesr and 1.8.x clients, 1.8.4 would likely be too old a release to expect smooth operations - there have been landings over a number of 1.8.x releases to address interop issues, starting with 1.8.5 but continuing with the Whamcloud 1.8.x releases. My suggestion would be to use the latest 1.8.x release if you plan to run in mixed 2.x-1.8.x mode.

Does this give you the information that you need?

Peter

Comment by Nicola Bianchi [ 30/May/12 ]

Peter,
thank you for the answer.

Regards
Nicola


***********************************************************************
Nicola Bianchi
CSCS - Swiss National Supercomputing Center
Via Trevano 131
CH-6900 Lugano (TI) Tel: + 41 (0)91 610 8233
Switzerland Email: nbianchi@cscs.ch
***********************************************************************

Comment by Peter Jones [ 01/Jun/12 ]

No problem Nicola. Please let me know if you have any further questions

Generated at Sat Feb 10 01:16:39 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.