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

Rayees Namathponnan commented on CLOUDSTACK-4458:
-------------------------------------------------

On the Primary Storage:

[root@nfs2 i-5-19-VMWARERETEST]# ls
3fbe5d8cd5e64c1984984b4d4bf6e02f-flat.vmdk  i-5-19-VMWARERETEST.nvram  
i-5-19-VMWARERETEST.vmx   ROOT-19-delta.vmdk  vmware.log
3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk       i-5-19-VMWARERETEST.vmsd   
i-5-19-VMWARERETEST.vmxf  ROOT-19.vmdk
[root@nfs2 i-5-19-VMWARERETEST]# pwd
/export/home/chandan/307PB-195-103/primary2/i-5-19-VMWARERETEST
[root@nfs2 i-5-19-VMWARERETEST]#
                
> [VMWare] Failed to create Snapshot on Data Disk because of backup snapshot 
> exception
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4458
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4458
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: VMware
>    Affects Versions: 4.2.0
>            Reporter: Rayees Namathponnan
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> ======================
> Steps to Reproduce the Bug:
> ======================
> 1. Deploy a VM using the default CentOS Template
> 2. Create and attach a volume to the deployed VM as its data disk.
> 3. Create File System on it and generate few files on the data disk.
> 4. Stop the VM.
> 5. Take the Snapshot of the Data disk.
> =================================
> Observation on Management Server Logs:
> =================================
> 2013-08-22 11:37:53,960 DEBUG [storage.snapshot.SnapshotManagerImpl] 
> (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Failed to 
> create snapshot
> com.cloud.utils.exception.CloudRuntimeException: backup snapshot exception: 
> Exception: java.lang.RuntimeException
> Message: File 
> []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was 
> not found
>         at 
> org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281)
>         at 
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137)
>         at 
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:256)
>         at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1004)
>         at 
> org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280)
>         at 
> com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703)
>         at 
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>         at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>         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)
> 2013-08-22 11:37:53,970 DEBUG [storage.volume.VolumeServiceImpl] 
> (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Take 
> snapshot: 28 failed
> com.cloud.utils.exception.CloudRuntimeException: Failed to create snapshot
>         at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1029)
>         at 
> org.apache.cloudstack.storage.volume.VolumeServiceImpl.takeSnapshot(VolumeServiceImpl.java:1280)
>         at 
> com.cloud.storage.VolumeManagerImpl.takeSnapshot(VolumeManagerImpl.java:2703)
>         at 
> org.apache.cloudstack.api.command.user.snapshot.CreateSnapshotCmd.execute(CreateSnapshotCmd.java:170)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>         at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>         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)
> Caused by: com.cloud.utils.exception.CloudRuntimeException: backup snapshot 
> exception: Exception: java.lang.RuntimeException
> Message: File 
> []/vmfs/volumes/f9418bb5-7dc9164d/3fbe5d8cd5e64c1984984b4d4bf6e02f.vmdk was 
> not found
>         at 
> org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:281)
>         at 
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.backupSnapshot(XenserverSnapshotStrategy.java:137)
>         at 
> org.apache.cloudstack.storage.snapshot.XenserverSnapshotStrategy.takeSnapshot(XenserverSnapshotStrategy.java:256)
>         at 
> com.cloud.storage.snapshot.SnapshotManagerImpl.takeSnapshot(SnapshotManagerImpl.java:1004)
>         ... 11 more
> 2013-08-22 11:37:53,982 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-3:job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ]) Complete 
> async job-104 = [ 37de7501-cd46-40df-9f33-3344d8b2c36f ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: Failed to create 
> snapshot due to an internal error creating snapshot for volume 28

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to