Project

General

Profile

Actions

Bug #47828

closed

librbd: validate that the stripe unit is at least 512 bytes

Added by Jason Dillaman over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The only validation that librbd currently performs on the stripe unit is that it's a multiple of the object size. However, that technically permits stripe units of 1 byte. Restrict the minimum stripe unit size to the historical 512 byte block size.

$ rbd create --size 1M --stripe-unit 1B --stripe-count=32 image
$ rbd info image
rbd image 'image':
    size 1 MiB in 32 objects
    order 22 (4 MiB objects)
    snapshot_count: 0
    id: 102bef4986b9
    block_name_prefix: rbd_data.102bef4986b9
    format: 2
    features: layering, striping, exclusive-lock, object-map, fast-diff, deep-flatten
    op_features: 
    flags: 
    create_timestamp: Sun Oct 11 17:30:31 2020
    access_timestamp: Sun Oct 11 17:30:31 2020
    modify_timestamp: Sun Oct 11 17:30:31 2020
    stripe unit: 1 B
    stripe count: 32

Related issues 1 (1 open0 closed)

Related to Dashboard - Bug #48851: mgr/dashboard: iSCSI exported RBD image stripe units must be a multiple of the SCSI block sizeNew

Actions
Actions #1

Updated by Jason Dillaman over 3 years ago

  • Status changed from New to In Progress
  • Assignee set to Jason Dillaman
Actions #2

Updated by Jason Dillaman over 3 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 38655
Actions #3

Updated by Mykola Golub over 3 years ago

  • Status changed from Fix Under Review to Resolved
Actions #4

Updated by Volker Theile over 3 years ago

  • Related to Bug #48851: mgr/dashboard: iSCSI exported RBD image stripe units must be a multiple of the SCSI block size added
Actions

Also available in: Atom PDF