| commit | cc070d59bc422945f83a89e9d60f749d0f82787d | |
| author | Alex Elder <elder@inktank.com> | |
| Sun, 21 Apr 2013 17:14:45 +0000 (21 12:14 -0500) | ||
| committer | Sage Weil <sage@inktank.com> | |
| Thu, 2 May 2013 04:19:21 +0000 (1 21:19 -0700) | ||
| tree | 710d6ad8501cecd11b57bf84c332c98acac95da6 | treesnapshot (tar.gz zip) |
| parent | 57385b51c3ffd0fed2dd9d5d8e4ec080c85ecbcd | commitdiff |
rbd: get and check striping parameters
If an rbd format 2 image indicates it supports the STRIPINGV2
feature we need to find out its stripe unit and stripe count in
order to know whether we can use it. We don't yet support fancy
striping fully, but if the default parameters are used the behavior
is indistinguishible from non-fancy striping.
This is necessary because some images require the STRIPINGV2 feature
even if they use the default parameters. (Which is to say the feature
bit was erroneously set even if the feature was not used.)
This resolves:
http://tracker.ceph.com/issues/4709
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
If an rbd format 2 image indicates it supports the STRIPINGV2
feature we need to find out its stripe unit and stripe count in
order to know whether we can use it. We don't yet support fancy
striping fully, but if the default parameters are used the behavior
is indistinguishible from non-fancy striping.
This is necessary because some images require the STRIPINGV2 feature
even if they use the default parameters. (Which is to say the feature
bit was erroneously set even if the feature was not used.)
This resolves:
http://tracker.ceph.com/issues/4709
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
| drivers/block/rbd.c | diffblobblamehistory |