NetApp iSCSI driver doesn't enforce 32 block-ranges limit
Bug #1288962 reported by
Andrew Kerr
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Andrew Kerr |
Bug Description
The NetApp zapi for clone create has an undocumented limit of 32 block ranges (of a max 2^24 blocks each).
The driver should check to make sure the number of block range segments does not exceed 32. In the case of an excessively large request, the xml may be rejected by the filer silently and the volume will become stuck in an extending state, with 2 flexVols (the original and the new sized one) present on the filer.
description: | updated |
Changed in cinder: | |
assignee: | nobody → Andrew Kerr (andrew-kerr) |
summary: |
- NetApp iSCSI driver doesn't enforce 32 block range limit + NetApp iSCSI driver doesn't enforce 32 block-ranges limit |
tags: | added: drivers |
Changed in cinder: | |
assignee: | Andrew Kerr (andrew-kerr) → Alex Meade (alex-meade) |
Changed in cinder: | |
assignee: | Alex Meade (alex-meade) → Andrew Kerr (andrew-kerr) |
Changed in cinder: | |
milestone: | none → icehouse-rc1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | icehouse-rc1 → 2014.1 |
To post a comment you must log in.
For cases when the range count exceeds 32, the clone call needs to be broken up into multiple calls with up to 32 ranges per call. In this way the practical limit is infinite.