Project

General

Profile

Actions
Copy link

Bug #48316

open

rgw: bi entry mtime discrepancy after incremental sync of versioned object

Added by Yehuda Sadeh over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Can happen when the object creation is followed by attribute change (such as acl) on the same object version. The object itself has the correct modification time, but the index entry refers to the original modification time. This would happen if the first sync of the object already retrieves the latest version. The link_olh operation maintains the mtime it got from the bi log.

No data to display

Actions
Copy link

Also available in: Atom PDF