new Jenkins VM in PHX lab

[Anton Marchukov]

Hello All.

Why do we need LVM at all there? It is good when you cannot resize the
underlying disk and have to combine it from several hardware ones into one
virtual. But here we have "cloud" and disks are already resizeable.

Anton.

On Wed, Feb 10, 2016 at 10:20 AM, Nadav Goldin <ngoldin at redhat.com> wrote:

> You forgot the 1st thing we told you - "don't create partitions on the
>> disk"...
>> Instead the whole disk '/dev/vdX' should be formatted as a PV, then you
>> can
>> grow it from the engine and then 'pvresize' followed by 'lvresize'.
>
>
> I didn't forget, I came across [1] which quotes [2] and [3] saying
> best-practice is to create a partition on the PV:
>
>> *Not Recommended*
>>
>> Using the whole disk as a PV (as opposed to a partition spanning the
>> whole disk) is not recommended because of the management issues it can
>> create. Any other OS that looks at the disk will not recognize the LVM
>> metadata and display the disk as being free, so it is likely it will be
>> overwritten. LVM itself will work fine with whole disk PVs.
>>
> although I am no expert in lvm so if we agree its ok, no problem, I'll
> change it.
>
> [1]
> http://unix.stackexchange.com/questions/76588/what-is-the-best-practice-for-adding-disks-in-lvm
> [2] http://tldp.org/HOWTO/LVM-HOWTO/initdisks.html
> [3]
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/LVM_components.html#multiple_partitions
>
>
> On Wed, Feb 10, 2016 at 11:02 AM, Barak Korren <bkorren at redhat.com> wrote:
>
>> > able to do "live" storage incrase by adding a new volume to the LVM
>> group in
>> > the following procedure:
>> >
>> >  created new virtio volume in the VM from phx-engine
>> >  fdisk /dev/vdd then: n -> p -> 1 -> enter -> enter -> t -> 8e -> w
>> >  vgextend jenkins_lvm /dev/vdd1
>> >  lvextend /dev/mapper/jenkins_lvm-data -L28G
>> >  xfs_growfs /dev/mapper/jenkins_lvm-data
>> >
>> > I was unable to increase the volume size from the engine, and then
>> increase
>> > the partition size(only create a new partition on the same volume with
>> the
>> > new increased space in the volume), not sure if that is possible.
>> >
>> You forgot the 1st thing we told you - "don't create partitions on the
>> disk"...
>> Instead the whole disk '/dev/vdX' should be formatted as a PV, then you
>> can
>> grow it from the engine and then 'pvresize' followed by 'lvresize'.
>>
>>
>> --
>> Barak Korren
>> bkorren at redhat.com
>> RHEV-CI Team
>>
>
>
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


-- 
Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20160210/4cda9fc2/attachment.html>