https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6086 Lustre <p>We require that MDTs and OSTs be running the same version of Lustre (i.e. no interoperability between MDTs) for DNE and LFSCK. While we always test this way and know this requirement ourselves, I know that there will be users who don't know this in the future, and I don't think this is actually checked or enforced anywhere.</p> <p>The MDTs and OSTs should check at connect time via <tt>ocd_version</tt> that the connecting server is running the same major version of Lustre (e.g. 2.5.x or 2.7.x). Otherwise we may run into interoperability issues if someone is trying to run different versions of Lustre on the MDTs (e.g. DNE1 2.5 - DNE2 2.6 , or DNE2 2.6 - DNE2 2.8 async_commit, or LFSCK changes like <a href="http://review.whamcloud.com/13172" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13172</a> or similar).</p> LU-6086

verify MDTs are running the same Lustre version

Improvement Major Resolved Fixed nasf Andreas Dilger Wed, 7 Jan 2015 05:47:16 +0000 Wed, 16 Mar 2016 13:53:54 +0000 Wed, 16 Mar 2016 13:53:54 +0000 Lustre 2.7.0 Lustre 2.5.5 Lustre 2.7.0 Lustre 2.5.5 0 6 <p>If the OST found that the MDT is running different version, should we forbid the connection? or forbid some LFSCK operations? Or just print some warning message on console?</p> <p>On the other hand, I am not sure whether it is part of the roll upgrade/downgrade among servers.</p> <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/13285" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13285</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6086" title="verify MDTs are running the same Lustre version" class="issue-link" data-issue-key="LU-6086"><del>LU-6086</del></a> obdclass: check peer's version for server connection<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 3ccbc301d2f987c6befed61459d6bcef9fc2b53a</p> <p>Fan Yong (fan.yong@intel.com) uploaded a new patch: <a href="http://review.whamcloud.com/13287" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13287</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6086" title="verify MDTs are running the same Lustre version" class="issue-link" data-issue-key="LU-6086"><del>LU-6086</del></a> obdclass: check peer's version for server connection<br/> Project: fs/lustre-release<br/> Branch: b2_5<br/> Current Patch Set: 1<br/> Commit: 9621c9fc081bf5a3866c188c3a4bd4de51a6e930</p> <p>I worry about rolling upgrades that could be one mds or one ost at a time</p> <p>I would say that we will only support the rolling upgrade between small versions, such as the patch version difference is within 3. But if rolling upgrade happens between major versions, such as from Lustre-2.6 to Lustre-2.7, it will get failure.</p> <p>Andreas, what's your thought for that?</p> <p>Oleg Drokin (oleg.drokin@intel.com) merged in patch <a href="http://review.whamcloud.com/13285/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/13285/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-6086" title="verify MDTs are running the same Lustre version" class="issue-link" data-issue-key="LU-6086"><del>LU-6086</del></a> obdclass: check peer's version for MDT-MDT connection<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 0030ed640284e4ed5afa9187c5a907141132b083</p> <p>Reopening/resolving to be able to adjust the Fix Version. This was entirely landed for 2.7. There is nothing landed here that was addressed in 2.8.</p> Related LU-6307 Development Rank 1|hzx3an: Rank (Obsolete) 16936