Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cephfs-journal-tool event get list added output 'event time' #20346

Closed
wants to merge 1 commit into from

Conversation

charmingcow
Copy link

@charmingcow charmingcow commented Feb 7, 2018

add event timestamp for tool output is useful, such as analyze the damaged mds journal
cephfs-journal-tool event get list
0x400000 SUBTREEMAP: ()
cephfs-journal-tool event get list
2018-02-07 12:37:02.417835 0x400000 SUBTREEMAP: ()

Signed-off-by: "Wang,Yong" wang.yong@datatom.com

Signed-off-by: wang yong <wang.yong@datatom.com>
@tchaikov tchaikov added this to the jewel milestone Feb 7, 2018
@charmingcow
Copy link
Author

Can anybody help to review it?

Copy link
Author

@charmingcow charmingcow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Contributor

@smithfarm smithfarm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First of all, thanks for contributing to Ceph.

This PR is targeting the wrong branch - should be "master".

Once the commit is in master, it can be cherry-picked to luminous and jewel.

To make that happen, open a tracker issue and fill in "luminous, jewel" into the "Backports" field.

Then, add a line saying "Fixes: https://tracker.ceph.com/issues/$ISSUE_NUMBER" to the commit.

Please also read https://github.com/ceph/ceph/blob/master/SubmittingPatches.rst#preparing-and-sending-patches for more info.

@smithfarm smithfarm removed this from the jewel milestone Feb 23, 2018
@smithfarm smithfarm added the DNM label Feb 23, 2018
@charmingcow charmingcow changed the base branch from jewel to master February 24, 2018 07:47
@charmingcow charmingcow changed the base branch from master to jewel February 24, 2018 13:10
@charmingcow charmingcow changed the base branch from jewel to master February 24, 2018 13:17
@charmingcow charmingcow changed the base branch from master to jewel-next February 24, 2018 13:18
@charmingcow charmingcow changed the base branch from jewel-next to jewel February 24, 2018 13:18
@charmingcow charmingcow changed the base branch from jewel to master February 24, 2018 15:12
@charmingcow
Copy link
Author

charmingcow commented Feb 24, 2018

Fixes: https://tracker.ceph.com/issues/23116
Signed-off-by: "Wang,Yong" wang.yong@datatom.com

@charmingcow
Copy link
Author

charmingcow commented Feb 24, 2018

@smithfarm once I changed to pr into branch master, there are a lot of files showned changed. should I close this PR,and copy codes to charmingcow/master then make a PR again?

@charmingcow charmingcow changed the base branch from master to jewel February 24, 2018 15:53
@smithfarm
Copy link
Contributor

smithfarm commented Feb 24, 2018

@charmingcow It's probably easier to start over and make a new PR targeting master, yes. And the "Fixes: https://tracker.ceph.com/issues/23116" line should be in the commit message (not just a comment in the PR).

@smithfarm
Copy link
Contributor

@charmingcow I see you opened #20580 so I'll close this now.

@smithfarm smithfarm closed this Feb 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants