Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
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.
Attachments
Activity
Link | Original: This issue is related to JFC-17 [ JFC-17 ] |
Link | New: This issue is related to JFC-20 [ JFC-20 ] |
Labels | Original: LTS |
Fix Version/s | New: Lustre 2.10.5 [ 14003 ] |
Link | Original: This issue is related to JFC-19 [ JFC-19 ] |
Link | Original: This issue is related to JFC-10 [ JFC-10 ] |
Link | New: This issue is related to JFC-17 [ JFC-17 ] |
Labels | New: LTS |
John L. Hammond (jhammond@whamcloud.com) merged in patch https://review.whamcloud.com/32525/
Subject:
LU-10989utils: correct lustre_rsync changelog clear logicProject: fs/lustre-release
Branch: b2_10
Current Patch Set:
Commit: a41b3782e4ffe961d7d0173845753a1ab23b5463