[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030053#comment-14030053
 ] 

Min Chen commented on CLOUDSTACK-6797:
--------------------------------------

Assigned to Marcus to investigate this issue since he is the expert on resize 
volume feature. Based on communication with Prashant, the problem is this: 
although resizeVolume did resource limit check and maxVolumeSize check in the 
flow, it didn't really check the real available storage space in a storage 
pool. For attached volume, it replies on sending resizeVolumeCommand to storage 
pool to error out, but for detached volume, it will succeed even though user 
gave a very large size that outnumber our storage pool capacity. Actually 
relying on sending resizeVolumeCommand to storage pool to error out is not an 
ideal solution, the better fix should be checking currently available space on 
storage pool to early abort if a big size is provided, just like how we did in 
StoragePoolAllocator to check whether a pool has enough space.

> 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: Min Chen
>            Priority: Critical
>             Fix For: 4.4.0
>
>         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.2#6252)

Reply via email to