Feature #3540: mds: maintain per-file backpointers on first file object - CephFS - Ceph

Actions

Copy link

Feature #3540

closed

mds: maintain per-file backpointers on first file object

Added by Sage Weil over 11 years ago. Updated about 11 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Sam Lang

Category:

Target version:

v0.60

% Done:

Source:

Tags:

Backport:

Reviewed:

Affected Versions:

Component(FS):

Labels (FS):

Pull request ID:

Description

Add backtraces to each file object, as described at http://www.spinics.net/lists/ceph-devel/msg11872.html. This ticket includes the MDS asynchronously updating backtraces on creates and renames, as well as the "sentinel object" infrastructure, but not the lookup infrastructure.

For this initial implementation, the MDS should add the backtrace on file create (so we end up with a sentinel for all objects whose pool gets changed).

Actions

Copy link

Updated by Sage Weil over 11 years ago

Translation missing: en.field_position deleted (1)
Translation missing: en.field_position set to 15

Actions

Copy link

Updated by Sage Weil over 11 years ago

Translation missing: en.field_story_points set to 13
Translation missing: en.field_position deleted (16)
Translation missing: en.field_position set to 16

Actions

Copy link

Updated by Greg Farnum over 11 years ago

Do we have any kind of design for this? We've talked about it some and it's conceptually simple, but splitting up the responsibility between client and MDS for doing this, and then making sure we clearly define the consistency guarantees and follow them, is going to take some work.

Actions

Copy link

Updated by Sage Weil over 11 years ago

Status changed from New to 12

Greg Farnum wrote:

Do we have any kind of design for this? We've talked about it some and it's conceptually simple, but splitting up the responsibility between client and MDS for doing this, and then making sure we clearly define the consistency guarantees and follow them, is going to take some work.

No concrete design yet. We need to discuss this as a team before implementing anything.

My initial thought is to have the mds to this, but if we have the client piggyback it on writeback that would be more efficient. Maybe that's v2.

Actions

Copy link

Updated by Greg Farnum over 11 years ago

Description updated (diff)

We have a design now!

Actions

Copy link

Updated by Greg Farnum over 11 years ago

Translation missing: en.field_story_points deleted (13)
Translation missing: en.field_position deleted (16)
Translation missing: en.field_position set to 16

Actions

Copy link

Updated by Sage Weil over 11 years ago

Translation missing: en.field_story_points set to 8
Translation missing: en.field_position deleted (17)
Translation missing: en.field_position set to 6

Actions

Copy link

Updated by Sage Weil over 11 years ago

Translation missing: en.field_position deleted (6)
Translation missing: en.field_position set to 2

Actions

Copy link

Updated by Sage Weil over 11 years ago

Target version set to v0.57c
Translation missing: en.field_position deleted (2)
Translation missing: en.field_position set to 2

Actions

Copy link

#10

Updated by Ian Colle over 11 years ago

Assignee set to Sam Lang

Actions

Copy link

#11

Updated by Sam Lang about 11 years ago

Status changed from 12 to In Progress

Actions

Copy link

#12

Updated by Sam Lang about 11 years ago

Status changed from In Progress to Fix Under Review

Initial implementation in wip-bt. Needs review.

Actions

Copy link

#13

Updated by Greg Farnum about 11 years ago

Status changed from Fix Under Review to In Progress

The initial review happened last week; Sam has some updates for the rename and sentinel object infrastructure now but they aren't ready for review.

Actions

Copy link

#14

Updated by Sam Lang about 11 years ago

Status changed from In Progress to 7

I've pushed the additional changes for rename and sentinel to the wip-bt2 branch. Those bits are still untested, but can probably be reviewed in the mean-time...

Actions

Copy link

#15