![\"VirtualDisk\"](\"https:\/\/www.asrivas.me\/blog\/wp-content\/uploads\/VirtualDisk.png\")
<\/a><\/p>\nThe disk will not be visible to the Guest OS directly; you may need to trigger a rescan of the devices. This is easy to do on Linux but it should be possible on any other Guest OS as well:<\/p>\n
where sdb1 is the new partition created on \/dev\/sdb. The next step is to create the physical volume for the partition and we can do this using the pvcreate command:<\/p>\n To extend a logical volume, we would first need to find out the name of the volume using the “vgdisplay” command. In the case of my setup, this is the output for “vgdisplay”:<\/p>\n Lets extend the mediaserver-vg volume using vgextend:<\/p>\n Lets do a pvscan to check if everything looks good:<\/p>\n root@mediaserver:~# vgdisplay <\/code><\/p>\n Now that we have added a physical volume to the VG, we need to extend the logical volume partition which is running out of space. Information about the LVs can be displayed using the lvdisplay command:<\/p>\n <\/code><\/p>\n Note that the LV size is only 28.74 GB and has not been extended by the extra 30GB that we added. We would need to use the “lvextend” command to do this:<\/p>\n root@mediaserver:~# lvdisplay <\/code> <\/p>\n So, we have extended our root partition volume to 58.73GB from 28.74GB (+30GB). The last step is to resize the filesystem to occupy the newly allocated space using resize2fs:<\/p>\n root@mediaserver:~# df -h <\/code><\/p>\n There, we have extended the root partition of a running VM without any downtime \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":" Logical volumes allow for flexibility of resizing system partitions on the fly without any downtime. This is a pretty nice feature to have in Guest OS since one does not have to worry too much about allocating the right amount of disk upfront. In a previous life, I have spent many a waking hour reinstalling … [Read more…]<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[],"_links":{"self":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/113"}],"collection":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/comments?post=113"}],"version-history":[{"count":4,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/113\/revisions"}],"predecessor-version":[{"id":224,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/posts\/113\/revisions\/224"}],"wp:attachment":[{"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/media?parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/categories?post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.asrivas.me\/blog\/wp-json\/wp\/v2\/tags?post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\necho \"0 0 0\" > \/sys\/class\/scsi_host\/host0\/scan
\nfdisk -l
\n<\/code>
\nNote that when I tried this on Ubuntu Server 16.04 LTS, it required a reboot to detect the disk. Once the disk is visible under \/dev, we can open the disk using cfdisk and create a partition on it. Lets also format it using ext4:<\/p>\n
\n mkfs.ext4 \/dev\/sdb1
\n<\/code><\/p>\n
\nroot@mediaserver:~# pvcreate \/dev\/sdb1
\n Physical volume \"\/dev\/sdb1\" successfully created
\n<\/code><\/p>\n
\nroot@mediaserver:~# vgdisplay
\n --- Volume group ---
\n VG Name mediaserver-vg
\n System ID
\n Format lvm2
\n Metadata Areas 1
\n Metadata Sequence No 5
\n VG Access read\/write
\n...
\n...
\n<\/code><\/p>\n
\nroot@mediaserver:~# vgextend mediaserver-vg \/dev\/sdb1
\n Volume group \"mediaserver-vg\" successfully extended
\n<\/code><\/p>\n
\nroot@mediaserver:~# pvscan
\n PV \/dev\/sda5 VG mediaserver-vg lvm2 [30.05 GiB \/ 324.00 MiB free]
\n PV \/dev\/sdb1 VG mediaserver-vg lvm2 [30.00 GiB \/ 30.00 GiB free]
\n Total: 2 [60.05 GiB] \/ in use: 2 [60.05 GiB] \/ in no VG: 0 [0 ]<\/p>\n
\n --- Volume group ---
\n VG Name mediaserver-vg
\n System ID
\n Format lvm2
\n Metadata Areas 2
\n Metadata Sequence No 6
\n VG Access read\/write
\n VG Status resizable
\n MAX LV 0
\n Cur LV 2
\n Open LV 2
\n Max PV 0
\n Cur PV 2
\n Act PV 2
\n VG Size 60.05 GiB
\n...
\n...<\/p>\n
\nroot@mediaserver:~# lvdisplay
\n --- Logical volume ---
\n LV Path \/dev\/mediaserver-vg\/root
\n LV Name root
\n VG Name mediaserver-vg
\n LV UUID NDkzNB-kyPq-4qZV-bpTr-rY8z-zqXr-jwpZeH
\n LV Write Access read\/write
\n LV Creation host, time ,
\n LV Status available
\n # open 1
\n LV Size 28.74 GiB<\/p>\n
\nroot@mediaserver:~# lvextend \/dev\/mediaserver-vg\/root \/dev\/sdb1
\n Extending logical volume root to 58.73 GiB
\n Logical volume root successfully resized<\/p>\n
\n --- Logical volume ---
\n LV Path \/dev\/mediaserver-vg\/root
\n LV Name root
\n VG Name mediaserver-vg
\n LV UUID NDkzNB-kyPq-4qZV-bpTr-rY8z-zqXr-jwpZeH
\n LV Write Access read\/write
\n LV Creation host, time ,
\n LV Status available
\n # open 1
\n LV Size 58.73 GiB<\/p>\n
\nroot@mediaserver:~# resize2fs \/dev\/mediaserver-vg\/root
\nresize2fs 1.42.9 (4-Feb-2014)
\nFilesystem at \/dev\/mediaserver-vg\/root is mounted on \/; on-line resizing required
\nold_desc_blocks = 2, new_desc_blocks = 4
\nThe filesystem on \/dev\/mediaserver-vg\/root is now 15396864 blocks long.<\/p>\n
\nFilesystem Size Used Avail Use% Mounted on
\n\/dev\/mapper\/mediaserver--vg-root 58G 12G 44G 22% \/<\/p>\n