re-installed and configured it without a partition table on the block device. the updated procedure for increasing the volume size: if there is still available space in the lvm group jenkins_lvm (can be seen using vgdisplay): 1. lvextend /dev/mapper/jenkins_lvm-data -L410G 2. xfs_growfs /dev/mapper/jenkins_lvm-data
else: 1. increase volume size in engine-ui 2. pvresize /dev/vdb 3. lvextend /dev/mapper/jenkins_lvm-data -L410G 4. xfs_growfs /dev/mapper/jenkins_lvm-data On Wed, Feb 10, 2016 at 11:54 AM, Barak Korren <[email protected]> wrote: > On 10 February 2016 at 11:22, Anton Marchukov <[email protected]> wrote: > > 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. > > > Becasue LVM lets you do snapshots you can mount and copy somewhere > else (e.g. to do atomic backups). You cannot do that easily with oVirt > disk snapshots ATM. > > > > -- > Barak Korren > [email protected] > RHEV-CI Team >
_______________________________________________ Infra mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/infra
