Project

General

Profile

Actions

Bug #53062

closed

OMAP upgrade to PER-PG format result in ill-formatted OMAP keys.

Added by Igor Fedotov over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Urgent
Assignee:
-
Target version:
-
% Done:

0%

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

Description

Looks like the code appends the full legacy key to the new prefix rather that use the user-provided OMAP name from the tail of the key.
So the resulting key gets the following format:
<new key prefix: <pool_id, hash, onode_nid>> + '.' + <legacy key prefix: <nid>> + '.' + <user name>
while the expected one is:
<new key prefix: <pool_id, hash, onode_nid>> + '.' + <user name>
Originally brought up here:
https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/XDMISQC74Z67RXP2PJHERARJ7KT2ADW4/
and here
https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/7PZWYBIB53G2TBVYE4TFOISKYEP3W4ND/


Related issues 3 (1 open2 closed)

Related to bluestore - Bug #53064: pgmeta onode isn't tagged with FLAG_PGMETA_OMAP if created in pre-mimic areNew

Actions
Has duplicate bluestore - Bug #53426: rbd_directory (and some others) corrupted after update from 15.2.10 to 16.2.6DuplicateIgor Fedotov

Actions
Copied to bluestore - Backport #53124: pacific: OMAP upgrade to PER-PG format result in ill-formatted OMAP keys.ResolvedIgor FedotovActions
Actions

Also available in: Atom PDF