Skip to content

Rescue procedure for extremely large bluefs log#36110

Closed
aclamk wants to merge 3 commits intoceph:masterfrom
aclamk:wip-bluefs-log-replay-rescue
Closed

Rescue procedure for extremely large bluefs log#36110
aclamk wants to merge 3 commits intoceph:masterfrom
aclamk:wip-bluefs-log-replay-rescue

Conversation

@aclamk
Copy link
Contributor

@aclamk aclamk commented Jul 15, 2020

This is procedure that stems from https://tracker.ceph.com/issues/46195.
It was created and tested in Luminous, but now needs to be ported to all other ceph branches.
This fixes https://tracker.ceph.com/issues/46552.

aclamk added 3 commits July 15, 2020 13:26
This is a procedure tries to find on disk unreachable extents and pretend they were
already a part of bluefs log. If this gives proper crc, accept it.

Fixes: https://tracker.ceph.com/issues/46195
Signed-off-by: Adam Kupczyk <akupczyk@redhat.com>
This ability only makes sense as a step that allows to perform fsck before commiting recovered bluefs log.

Signed-off-by: Adam Kupczyk <akupczyk@redhat.com>
Adds additional paragraph to ceph-bluestore-tool documentation,
describing how to use *special* options --bluefs_replay_recovery
and --bluefs_replay_recovery_disable_compact to recover large
bluefs log.

Signed-off-by: Adam Kupczyk <akupczyk@redhat.com>
@aclamk
Copy link
Contributor Author

aclamk commented Jul 15, 2020

Superseded by #36121

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants