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
tools/erasure-code: new tool to encode/decode files #34090
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tchaikov
reviewed
Mar 24, 2020
trociny
force-pushed
the
wip-ceph-erasure-code-tool
branch
from
March 25, 2020 08:58
2c60c06
to
fdf3926
Compare
Updated. The build packages: https://shaman.ceph.com/repos/ceph/wip-mgolub-testing/fdf3926df131c016ddf03b290fd12fcf2a3ab9b4/ |
jdurgin
approved these changes
Mar 27, 2020
tchaikov
reviewed
Apr 11, 2020
trociny
force-pushed
the
wip-ceph-erasure-code-tool
branch
2 times, most recently
from
April 13, 2020 17:18
d525249
to
34b1eb6
Compare
@tchaikov other comments are addressed. Thanks. |
trociny
force-pushed
the
wip-ceph-erasure-code-tool
branch
from
April 13, 2020 17:22
34b1eb6
to
dbe2f25
Compare
E.g. it may be useful as a last resort when recovering an object from a damaged PG: extract the encoded object chunks from the PG shards with ceph-objectstore-tool and then decode with ceph-erasure-code-tool. It also has functionality similar to what ceph_erasure_code test provides. Signed-off-by: Mykola Golub <mgolub@suse.com>
Signed-off-by: Mykola Golub <mgolub@suse.com>
Its functionality is moved to ceph-erasure-code-tool. Signed-off-by: Mykola Golub <mgolub@suse.com>
trociny
force-pushed
the
wip-ceph-erasure-code-tool
branch
from
April 13, 2020 17:26
dbe2f25
to
56aaaf8
Compare
Sorry, repushed -- there had been some mess after rebase. |
tchaikov
approved these changes
Apr 14, 2020
This was referenced Oct 4, 2021
@trociny is there a pacific backport as well for this PR? |
@ideepika This PR was merged to a pre-pacific master so no need in a pacific backport. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
E.g. it may be useful as a last resort when recovering an object from
a damaged PG: extract the encoded object chunks from the PG shards
with ceph-objectstore-tool and then decode with ceph-erasure-code-tool.
Signed-off-by: Mykola Golub mgolub@suse.com
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard backend
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox