cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-3788) [KVM] Weekly Snapshot got stuck in "Allocated State"
Date Wed, 07 Aug 2013 22:28:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Fang Wang resolved CLOUDSTACK-3788.
-----------------------------------

    Resolution: Won't Fix

The hourly snapshot and weekly snapshot occurred at the same time, which caused one stuck.


We would not recommend users to take hourly and weekly snapshots at the same time. We could
have better error reporting scheme for this operation. But it is not a critical issue. 
                
> [KVM] Weekly Snapshot got stuck in "Allocated State"
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-3788
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3788
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Fang Wang
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.log.2013-07-23.gz, mysql_cloudstack_dump.zip
>
>
> Weekly Snapshot stuck in Allocated State:
> mysql> select * from snapshots where name like "Atoms-VM-1_ROOT-6_20130723235146";
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+----------------------------------+--------------------------------------+---------------+------------------+--------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> | id | data_center_id | account_id | domain_id | volume_id | disk_offering_id | status
   | path | name                             | uuid                                 | snapshot_type
| type_description | size   | created             | removed | backup_snap_id | swift_id |
sechost_id | prev_snap_id | hypervisor_type | version | s3_id |
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+----------------------------------+--------------------------------------+---------------+------------------+--------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> | 24 |              1 |          3 |         1 |         6 |                1 | Destroyed
| NULL | Atoms-VM-1_ROOT-6_20130723235146 | 08a0d2aa-9635-41cd-ba54-5367303bceac |       
     3 | HOURLY           | 147456 | 2013-07-23 23:51:46 | NULL    | NULL           |    
NULL |       NULL |         NULL | KVM             | 2.2     |  NULL |
> | 25 |              1 |          3 |         1 |         6 |                1 | Allocated
| NULL | Atoms-VM-1_ROOT-6_20130723235146 | 1e24a056-be38-4b55-845b-a5672b9fa93c |       
     5 | WEEKLY           | 147456 | 2013-07-23 23:51:46 | NULL    | NULL           |    
NULL |       NULL |         NULL | KVM             | 2.2     |  NULL |
> +----+----------------+------------+-----------+-----------+------------------+-----------+------+----------------------------------+--------------------------------------+---------------+------------------+--------+---------------------+---------+----------------+----------+------------+--------------+-----------------+---------+-------+
> 2 rows in set (0.04 sec)
> Attached Management Server logs and cloud database dump

--
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

Mime
View raw message