Bug #6279: creating a new fs on pools from an old fs can lead to lost MDS Tables - CephFS - Ceph

Actions

Copy link

Bug #6279

closed

creating a new fs on pools from an old fs can lead to lost MDS Tables

Added by Greg Farnum over 10 years ago. Updated almost 8 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

% Done:

Source:

Community (dev)

Tags:

Backport:

dumpling

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

MDS

Labels (FS):

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

See the thread at http://www.mail-archive.com/ceph-users@lists.ceph.com/msg03918.html

If you delete your FS (but not the data pools), then create a new FS on the same pools, the MDS client IDs are repeated. This means that if you haven't started recycling ops in the PG log, the OSDs will incorrectly return success on writes without doing anything. This can lead to eg not having a snaptable on disk, because the MDS tries to write out the initial one and the OSD says "I already have that tid, and the op succeeded" and short-circuits.

The best solution I've come up with so far is to somehow add an FS generation number to the MDS entity/invocation stuff, but I don't like having to maintain or steal that number in the Monitors...