[Users] SAN storage expansion

Elad Ben Aharon ebenahar at redhat.com
Thu Mar 20 12:07:00 UTC 2014


Daniel?

----- Original Message -----
From: "Giorgio Bersano" <giorgio.bersano at gmail.com>
To: "Elad Ben Aharon" <ebenahar at redhat.com>
Cc: "users at ovirt.org" <Users at ovirt.org>, "Daniel Erez" <derez at redhat.com>, "Gadi Ickowicz" <gickowic at redhat.com>, "Liron Aravot" <laravot at redhat.com>
Sent: Wednesday, March 19, 2014 4:12:35 PM
Subject: Re: [Users] SAN storage expansion

2014-03-18 10:28 GMT+01:00 Giorgio Bersano <giorgio.bersano at gmail.com>:
> 2014-03-18 9:15 GMT+01:00 Elad Ben Aharon <ebenahar at redhat.com>:
>> Hi,
>>
>> LUNs size are being updated using the multipath mechanism. In order to update storage domain size, you'll need to update the physical volume size using LVM on you hypervisors.
>>
>> Please do the following:
>> 1) Put the storage domain to maintenance
>> 2) Execute on your hosts:
>> 'pvresize --setphysicalvolumesize' with the new physical volume size (150G)
>> 3) Activate the storage domain
>
> Thank you Elad,
> I knew it was required a pvresize command but wanted to be sure that I
> wasn't disrupting possible storage parameters bookkeeping by the oVirt
> system.
> I'm wondering if it's because of this that SD has to be put in maintenance.
>
> Any chance to have the SD resize without putting it offline, for
> example doing pvresize on the SPM node and then pvscan on every other
> host involved?
> I'm sure there are use cases where this is would be of great convenience.
>

Well, I'm back on this.
First of all, Elad, your procedure works indeed.

Moreover, I tried this sequence:
1) Expand the volume using storage specific tools

2) on the SPM host execute
 pvresize /path/of/the/physical/volume  # (no need to specify the
size, it takes the full volume space)

3) (just to be sure) on every other host involved execute
 pvscan

4) the SD is shown with correct, updated, informations.

Maybe I am overzealous but I prefer to ask the experts:
Not putting the SD to maintenance could give unexpected consequences?

TIA,
Giorgio.


>> ----- Original Message -----
>> From: "Giorgio Bersano" <giorgio.bersano at gmail.com>
>> To: "users at ovirt.org" <Users at ovirt.org>
>> Sent: Monday, March 17, 2014 7:25:36 PM
>> Subject: [Users] SAN storage expansion
>>
>> Hi all,
>> I'm happily continuing my experiments with oVirt and I need a
>> suggestion regarding storage management.
>>
>> I'm using an iSCSI based Storage Domain and I'm trying to understand
>> which is the correct way to extend it's size some time after it's
>> creation.
>>
>> Please consider the following steps:
>>
>> 1) Using storage specific tools create a new volume on iSCSI storage
>> (e.g. 130.0 GiB)
>>
>> 2) in oVirt webadmin: Storage -> New Domain , select the previously
>> created storage (130 GB), OK, after some time it's online:
>>  Size: 129 GB ; Available: 125 GB ; Used: 4 GB
>>
>> 3) Use according to your needs (even noop is OK)
>>
>> 4) Using storage specific tools expand the new volume (e.g. 20.0 GiB
>> more, now it says 150.0GiB)
>>
>> 5) in webadmin: Storage, click on the domain, Edit. Looking at
>> Luns>Targets , now it correctly sees 150GB
>>
>> BUT
>> on the Storage tab it continues to be seen with
>>  Size: 129 GB ; Available: 125 GB ; Used: 4 GB
>>
>>
>> Do you think it is possible to make oVirt aware of the new available
>> storage space? Am I missing something obvious?
>>
>> My setup is oVirt 3.4.0 RC2 with fully patched CentOS 6.5 hosts.
>>
>> Best regards,
>> Giorgio.
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users



More information about the Users mailing list