[LU-10989] lustre_rsync may clear an unconsumed record after a CL_RENAME Created: 02/May/18 Updated: 01/Aug/18 Resolved: 17/May/18 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.12.0, Lustre 2.10.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | John Hammond | Assignee: | John Hammond |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
In lr_replicate(), if we see a non-extended rename record then we consume the following record to get the rename source. lr_clear_cl() accounts for this by adding 1 to the endrc if the current record is a rename. However, lr_clear_cl() always does this even if the current record was an extended rename. |
| Comments |
| Comment by Gerrit Updater [ 02/May/18 ] |
|
John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/32247 |
| Comment by Gerrit Updater [ 17/May/18 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/32247/ |
| Comment by Peter Jones [ 17/May/18 ] |
|
Landed for 2.12 |
| Comment by Gerrit Updater [ 23/May/18 ] |
|
Minh Diep (minh.diep@intel.com) uploaded a new patch: https://review.whamcloud.com/32525 |
| Comment by Gerrit Updater [ 01/Aug/18 ] |
|
John L. Hammond (jhammond@whamcloud.com) merged in patch https://review.whamcloud.com/32525/ |