Open Stack

I think the extend the size the volume is reasonable and easy
implementable. But the shrink of the LV is very dangerous. So add the
feature of extends the Volume size for the Cinder is OK.

Could you guys agree with me?


On Wed, Nov 28, 2012 at 12:56 PM, John Griffith <john.griffith at solidfire.com
> wrote:

>
>
> On Tue, Nov 27, 2012 at 7:19 PM, Matt Joyce <matt.joyce at cloudscaling.com>wrote:
>
>> other hazard to mention.
>>
>> live fs resizes tend to be sketchy.  the growing of a live filesystem is
>> possible and tends to work.  but shrinking for obvious reasons is very
>> dangerous and can be wrought with peril.  also cannot be done live as far
>> as I know for any ext filesystem.
>>
>> -matt
>>
>> On Tue, Nov 27, 2012 at 6:13 PM, Lei Zhang <zhang.lei.fly at gmail.com>wrote:
>>
>>>  Got it.
>>>
>>> Could Cinder can check the created volume? I can not find any command
>>> like cinder update. I try to extends the volume by lvextend, but data
>>> in the cinder db doesn't update. So when I delete the changed volume, it
>>> raise error.
>>>
>>> On Tue, Nov 27, 2012 at 12:34 PM, Dean Troyer <dtroyer at gmail.com>
>>> wrote:
>>>
>>> On Mon, Nov 26, 2012 at 8:04 PM, Lei Zhang <zhang.lei.fly at gmail.com>
>>>> wrote:
>>>> > Another question. If the vm treat the vol-0 as a normal block device,
>>>> is it
>>>> > necessary to partition? If not, the fdisk will show Disk /dev/vdb
>>>> doesn't
>>>> > contain a valid partition table. If yes, how can I extend the volume
>>>> on the
>>>> > vm? It seems that treat the volume as a normal block device is not a
>>>> good
>>>> > idea.
>>>>
>>>> It is not necessary to partition the device (vdb) inside com-0.  If
>>>> you use it as an LVM physical device (PV) inside com-0 then pvresize
>>>> will update the metadata o recognize the new size inside com-0 after
>>>> you lvextend the vol-0 in the host.
>>>>
>>>> If you do partition /dev/vdb and don't use LVM in com-0 it is still
>>>> possible to grow a partition, but you'll have to delete and re-create
>>>> the last partition to get com-0 to recognize the additional space.
>>>> And you'd also need to do the filesystem resize too.
>>>>
>>>> Nested LVM can be tricky but if you are careful to keep the layers
>>>> separated it can work.
>>>>
>>>> dt
>>>>
>>>> --
>>>>
>>>> Dean Troyer
>>>> dtroyer at gmail.com
>>>>
>>> --
>>> Lei Zhang
>>>
>>> Blog: http://jeffrey4l.github.com
>>> twitter/weibo: @jeffrey4l
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack at lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
> There is no functionality to re-size a Cinder Volume.
>
> John
>



-- 
Lei Zhang

Blog: http://jeffrey4l.github.com
twitter/weibo: @jeffrey4l
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121128/b477c353/attachment.html>