Actions
Bug #3656
closeddocs: "foo" doesn't mean anything in rbd example
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Someone named "Ugis" on the mailing list was having trouble
with the rbd command. One of the things this person mentioned
was this:
From: Ugis <ugis22@gmail.com> Subject: rbd kernel module crashes with different kernels ... well, I do not understand what in doc (http://ceph.com/docs/master/rbd/rbd-ko/) is meant by "myimage" so I am ommiting that part, but in no way kernel should crash if wrongly passed command has been given. Excerpt from doc: sudo rbd map foo --pool rbd myimage --id admin --keyring /path/to/keyring sudo rbd map foo --pool rbd myimage --id admin --keyfile /path/to/file
And then in a subsequent message referring to this:
Anyone can explain what is "foo" and "myimage" meaning here? Wich one is image name in pool and what is the other for?
I'm pretty sure "foo" is crap. And "myimage" should be "{image-name}"
in order to fit with the context around it.
Please verify this is a problem, though, I'm not an expert in
the usage of the rbd CLI...
Updated by John Wilkins over 11 years ago
- Status changed from New to In Progress
Updated by John Wilkins over 11 years ago
- Status changed from In Progress to Resolved
Apparently foo was the image name, and myimage was added and foo not removed.
Actions