[
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991297#comment-14991297
]
Wei Zhou commented on CLOUDSTACK-6797:
--------------------------------------
[~shadowsor]] I agree with Marcus. We should not disallow the volume resize of
detached volumes. it works most of time.
A better way might be checking the allocate capacity of pool when it is created
on primary storage (from Allocated to Ready), and checking the allocate
capacity of cluster (where the vm is) when it is attached.
> volume resize should not be allowed for detached volumes
> --------------------------------------------------------
>
> Key: CLOUDSTACK-6797
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6797
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0, 4.4.0
> Reporter: prashant kumar mishra
> Assignee: Marcus Sorensen
> Priority: Critical
> Fix For: Future
>
> Attachments: Logs_db.rar, screenshot-1.jpg, screenshot-2.jpg
>
>
> =>since resize space is counted in allocated space even though it cant be
> attach to VM , other storage operation will fail because threshold value
> If resize is allowed in volume detach
> ==============================
> 1-since there is no check for how much can be increased , suppose user has
> resized it to 1000GB
> 2-when user try to attach volume to vm it will fail since available space is
> not sufficient .
> 3-even though user is not able to use the resized volume ,CS will count
> 1000GB in allocated storage .
> 4-Dash will show allocated percentage >100%
> 5-Because threshold values , we cant perform any operation to that PS
> If resize is allowed online ( volume Attach) state it will fail in first
> place and will not cause any problem
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
