Hi Marty, I was able to solve it. Management log showed that I had an invalid size. After I changed the disk offering to be within the maximum size 20400 GB I am able to create the volumes of this size.
Thank you for a quick reply :) 2014-04-25 13:28:29,177 DEBUG [agent.transport.Request] (DirectAgent-341:null) Seq 3-1824278021: Processing: { Ans: , MgmtId: 42026829063690, via: 3, Ver: v1, Flags: 110, [{"storage.CreateAnswer":{"requestTemplateReload":false,"result":false,"details":"Exception: com.xensource.xenapi.Types$XenAPIException\nMessage: null\nStack: SR_BACKEND_FAILURE_79VDI Invalid size [opterr=VDI size must be between 1 MB and 2093049 MB]\n\tat com.xensource.xenapi.Types.checkResponse(Types.java:1731)\n\tat com.xensource.xenapi.Connection.dispatch(Connection.java:372)\n\tat com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:905)\n\tat com.xensource.xenapi.VDI.create(VDI.java:351)\n\tat com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:5561)\n\tat com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:405)\n\tat com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:69)\n\tat com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:187)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)\n\tat java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:166)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)\n\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)\n\tat java.lang.Thread.run(Thread.java:679)\n","wait":0}}] } 2014-04-25 13:28:29,177 DEBUG [agent.manager.AgentAttache] (DirectAgent-341:null) Seq 3-1824278021: No more commands found 2014-04-25 13:28:29,178 DEBUG [agent.transport.Request] (Job-Executor-75:job-3909) Seq 3-1824278021: Received: { Ans: , MgmtId: 42026829063690, via: 3, Ver: v1, Flags: 110, { CreateAnswer } } 2014-04-25 13:28:29,178 DEBUG [cloud.storage.StorageManagerImpl] (Job-Executor-75:job-3909) Retrying the create because it failed on pool Pool[205|NetworkFilesystem] 2014-04-25 13:28:29,195 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-75:job-3909) Looking for pools in dc: 1 pod:1 cluster:1 having tags:[sas] 2014-04-25 13:28:29,203 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-75:job-3909) FirstFitStoragePoolAllocator has 1 pools to check for allocation 2014-04-25 13:28:29,203 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-75:job-3909) Checking if storage pool is suitable, name: NJR2-Z1-P1-C1-D2 ,poolId: 205 2014-04-25 13:28:29,203 DEBUG [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-75:job-3909) StoragePool is in avoid set, skipping this pool 2014-04-25 13:28:29,203 DEBUG [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-75:job-3909) FirstFitStoragePoolAllocator returning 0 suitable storage pools 2014-04-25 13:28:29,203 WARN [cloud.storage.StorageManagerImpl] (Job-Executor-75:job-3909) Unable to find storage poll when create volume petervol02 2014-04-25 13:28:29,238 ERROR [cloud.api.ApiDispatcher] (Job-Executor-75:job-3909) Exception while executing AttachVolumeCmd: com.cloud.utils.exception.CloudRuntimeException: Failed to create volume when attaching it to VM: QB at com.cloud.vm.UserVmManagerImpl.attachVolumeToVM(UserVmManagerImpl.java:695) at com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:32) at com.cloud.api.commands.AttachVolumeCmd.execute(AttachVolumeCmd.java:118) at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:235) at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Peter Sadowski Director, Systems Engineering Email psadow...@dbr360.com Office +1 201 623 3604 Mobile +1 201 988 9679 DBR360 www.dbr360.com 1 Meadowlads Plaza 15th Floor East Rutherford, NJ 07073 This email and any attachments may be confidential and protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the e-mail or any attachment is prohibited. If you have received this email in error, please notify us immediately by replying to the sender and then delete this copy and the reply from your system. Thank you for your cooperation. -----Original Message----- From: Marty Sweet [mailto:msweet....@gmail.com] Sent: Friday, April 25, 2014 1:59 PM To: users@cloudstack.apache.org Subject: Re: Volume attach fails Hi Peter, What is your 'storage.max.volume.size' in the CloudStack Global Settings? Marty On 25 April 2014 16:41, Peter Sadowski <psadow...@dbr360.com> wrote: > I'm having a strange issue on cloudstack 3.0.5 when trying to attach a volume > to a VM. > I created a new Disk offering, 2TB with sas tag. I have 1TB and others as > well, which work no problem. > When I try to attach it I get the following error in the api > > > 2014-04-25 11:33:55,445 INFO [cloud.api.ApiServer] (catalina-exec-19:null) > (userId=4 accountId=4 sessionId=null) 172.31.1.14 -- GET > _=1398440030676&apikey=w77WYyAo6aUzQCIhE2nwIIcagD2omDGGonVFADdZHvMEwkz0FZh3DyBLf-bLqFRdxnyzAXT8-cHZp09pvn9aEw&command=queryAsyncJobResult&jobid=bb9e1367-3f9c-4a4f-910b-352afaeeb2c7&response=json&sessionkey=7isZzTuZqnUqjs%2B7lIjMFU6zi4A%3D&tenant=17a9fdec-30f0-4ed7-867c-c9b355b37b96&signature=xd3zOM01FG%2FY4%2BDaboLvigIT6R8%3D > 200 { "queryasyncjobresultresponse" : > {"accountid":"c5965828-afa1-4536-a67a-7a7034192e2d","userid":"2d01b436-cbf5-46a2-8271-61949ceaa51e","cmd":"com.cloud.api.commands.AttachVolumeCmd","jobstatus":2,"jobprocstatus":0,"jobresultcode":530,"jobresulttype":"object","jobresult":{"errorcode":530,"errortext":"Internal > error executing command, please contact your system > administrator"},"created":"2014-04-25T11:33:50-0400","jobid":"bb9e1367-3f9c-4a4f-910b-352afaeeb2c7"} > } > > Then the database entry shows the state as creating, but it never attaches or > creates the file on my NFS storage: > > mysql> select * from volumes where name like 'test222%'\G > *************************** 1. row *************************** > id: 376 > account_id: 4 > domain_id: 4 > pool_id: NULL > last_pool_id: NULL > instance_id: NULL > device_id: NULL > name: test222 > uuid: a386dfb6-f012-44a9-82c0-040d68bddf80 > size: 2199023255552 > folder: NULL > path: NULL > pod_id: NULL > data_center_id: 1 > iscsi_name: NULL > host_ip: NULL > volume_type: DATADISK > pool_type: NULL > disk_offering_id: 55 > template_id: NULL > first_snapshot_backup_uuid: NULL > recreatable: 0 > created: 2014-04-25 15:33:28 > attached: NULL > updated: 2014-04-25 15:33:50 > removed: NULL > state: Creating > chain_info: NULL > update_count: 1 > 1 row in set (0.00 sec)