Thank you Fred for your answer,
Aharon suggests me :
"
The flow should be like below -

 * Put the relevant domain in maintenance
 * Extend the lun (from storage side)
 * Resize the relevant PV (for example - > "pvresize
   --setphysicalvolumesize 125G >
   /dev/mapper/3600601601282300056f0075c3f81e311"
 * Activate the domain

Check the storage domain total size, It should have the new size.
"

I have a few question to do it manually:

 * Do I have to shutdown or live storage migrate to an other lun all my
   vms to perform the pv extend on the SPM? I know now it won't update
   the ovirt db but, is it a risk to do extend this in production?
 * My next question is : is it possible to fill manually the new lun
   size in the DB?

All this would prevent me from a heavy maintenance or from a very long migration (4TB) due to maintenance mode.

Le 16/03/2015 15:20, Fred Rolland a écrit :
Nathanael hi,

There is an open bug on this scenario :
https://bugzilla.redhat.com/show_bug.cgi?id=609689

Here are manual steps for overcome this issue:
https://access.redhat.com/solutions/376873


We are working on a solution for 3.6
http://www.ovirt.org/Features/LUN_Resize

Regards,

Fred

----- Original Message -----
From: "Nathanaël Blanchet" <[email protected]>
To: [email protected]
Sent: Monday, March 2, 2015 6:35:30 PM
Subject: [ovirt-users] expanding a lun on the san side

Hi all,

I've just expanded  the lun used as master by the domain storage. fdisk
on the SPM is able to see the multipath device with its new size, but
engine reports the old size.
How to refresh this?


_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to