yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20462
[Bug 1341459] Re: block device isn't resized after swap to larger volume
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => juno-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1341459
Title:
block device isn't resized after swap to larger volume
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
libvirt support swap volume. But if the new volume is larger than the
old one, the block device isn't resized. The instance can't see the
extra space.
$ nova show vm3
+--------------------------------------+----------------------------------------------------------------+
| Property | Value |
+--------------------------------------+----------------------------------------------------------------+
| OS-DCF:diskConfig | AUTO |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-SRV-ATTR:host | os3 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | os3 |
| OS-EXT-SRV-ATTR:instance_name | instance-00000039 |
| OS-EXT-STS:power_state | 1 |
| OS-EXT-STS:task_state | - |
| OS-EXT-STS:vm_state | active |
| OS-SRV-USG:launched_at | 2014-07-14T01:43:31.000000 |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2014-07-14T01:43:23Z |
| flavor | m1.nano (42) |
| hostId | c8e8cab21e9e22dbc3779fd171e77f44940ba1c81161dc114ba4ad85 |
| id | ccda09b7-6c50-40b0-ba7c-0c5c3f0cbb7e |
| image | cirros-0.3.2-x86_64-uec (da82a342-aeac-407a-bf9d-cf28bf68dc6b) |
| key_name | - |
| metadata | {} |
| name | vm3 |
| net1 network | 10.0.0.66 |
| os-extended-volumes:volumes_attached | [{"id": "756d0869-2ef2-4537-90c8-66df9657135f"}] |
| progress | 0 |
| security_groups | sg1, default |
| status | ACTIVE |
| tenant_id | fdbb1e8f23eb40c89f3a677e2621b95c |
| updated | 2014-07-14T06:34:57Z |
| user_id | 158d3c971e244f479593c86ff751bf8f |
+--------------------------------------+----------------------------------------------------------------+
$ cinder list
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
| 13097504-5b0c-4581-b1a5-9e05f616b89d | available | vol3 | 2 | None | false | |
| 756d0869-2ef2-4537-90c8-66df9657135f | in-use | vol1 | 1 | None | false | ccda09b7-6c50-40b0-ba7c-0c5c3f0cbb7e |
| f0da7609-486d-49b1-bdf3-029bcbe56268 | available | vol2 | 1 | None | false | |
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
Then login guest OS:
$ sudo fdisk -l
.....
Disk /dev/vdc: 1073 MB, 1073741824 bytes
9 heads, 8 sectors/track, 29127 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd6091017
Device Boot Start End Blocks Id System
/dev/vdc1 2048 2097151 1047552 83 Linux
Swap the volume to larger one.
$ nova volume-update vm3 756d0869-2ef2-4537-90c8-66df9657135f 13097504-5b0c-4581-b1a5-9e05f616b89d
vm3 attached with the vol3
$ cinder list
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
| 13097504-5b0c-4581-b1a5-9e05f616b89d | in-use | vol3 | 2 | None | false | ccda09b7-6c50-40b0-ba7c-0c5c3f0cbb7e |
| 756d0869-2ef2-4537-90c8-66df9657135f | available | vol1 | 1 | None | false | |
| f0da7609-486d-49b1-bdf3-029bcbe56268 | available | vol2 | 1 | None | false | |
+--------------------------------------+-----------+------+------+-------------+----------+--------------------------------------+
Check the guest again:
$ sudo fdisk -l
....
Disk /dev/vdc: 1073 MB, 1073741824 bytes
9 heads, 8 sectors/track, 29127 cylinders, total 2097152 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd6091017
Device Boot Start End Blocks Id System
/dev/vdc1 2048 2097151 1047552 83 Linux
The device size isn't changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1341459/+subscriptions
References