[LU-13087] The server highest transno can be lost, client reports 'went back in time'

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.14.0, Lustre 2.12.4
• Severity: 3
• Assignee: Mikhail Pershin
• Reporter: Mikhail Pershin

Description

The server highest transno can be lost after second-in-row failover due to uninitialized in-memory parameter lcd_last_transno

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/37187/
Subject: LU-13087 target: init lcd last transno from reply data
Project: fs/lustre-release
Branch: b2_12
Current Patch Set:
Commit: ae616d1b79cabccecaac74f84f9d614b0013f6d6

[Gerrit Updater]

Minh Diep ([e-mail]) uploaded a new patch: https://review.whamcloud.com/37187
Subject: LU-13087 target: init lcd last transno from reply data
Project: fs/lustre-release
Branch: b2_12
Current Patch Set: 1
Commit: 74a519bcd6ebe12e91dc990e5ad42d71f6064c6f

[Peter Jones]

Landed for 2.14

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/37060/
Subject: LU-13087 target: init lcd last transno from reply data
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 52c1cbaa7db7505642b64b2d85448d506a444661

[Gerrit Updater]

Mike Pershin ([e-mail]) uploaded a new patch: https://review.whamcloud.com/37060
Subject: LU-13087 target: init lcd last transno from reply data
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: bd70b50f5747aa804b272b0ae312cd742f8a52fe