{"id":290,"date":"2026-03-29T10:28:06","date_gmt":"2026-03-29T13:28:06","guid":{"rendered":"https:\/\/www.bernabauer.com\/blog\/?p=290"},"modified":"2026-05-21T09:03:59","modified_gmt":"2026-05-21T12:03:59","slug":"como-aumentar-o-tamanho-do-disco-de-uma-vm-ubuntu-no-virtualbox-com-lvm","status":"publish","type":"post","link":"https:\/\/www.bernabauer.com\/blog\/como-aumentar-o-tamanho-do-disco-de-uma-vm-ubuntu-no-virtualbox-com-lvm\/","title":{"rendered":"Como aumentar o tamanho do disco de uma VM Ubuntu no VirtualBox (com LVM)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Se voc\u00ea aumentou o disco virtual no VirtualBox, mas o Ubuntu continua mostrando pouco espa\u00e7o livre, este guia resolve o problema completo.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Esse cen\u00e1rio \u00e9 muito comum quando a VM usa\u00a0<strong>LVM<\/strong>: o disco virtual cresce, mas a parti\u00e7\u00e3o, o volume f\u00edsico, o volume group, o volume l\u00f3gico e o filesystem\u00a0<strong>n\u00e3o crescem sozinhos<\/strong>. O VirtualBox expande a imagem do disco com\u00a0<code>VBoxManage <a href=\"https:\/\/docs.oracle.com\/en\/virtualization\/virtualbox\/6.0\/user\/vboxmanage-modifymedium.html\">modifymedium<\/a> --resize<\/code>, e depois o sistema Linux precisa ser ajustado por dentro.\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Neste tutorial, vou mostrar como sair de algo como&nbsp;<strong>25 GB<\/strong>&nbsp;para&nbsp;<strong>50 GB<\/strong>&nbsp;em uma VM Ubuntu no VirtualBox.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Quando este tutorial se aplica<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Este passo a passo \u00e9 ideal para quem est\u00e1 em um cen\u00e1rio parecido com este:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>VM Ubuntu rodando no VirtualBox<\/li>\n\n\n\n<li>disco virtual em VDI<\/li>\n\n\n\n<li>sistema com LVM<\/li>\n\n\n\n<li><code>\/boot<\/code>\u00a0em parti\u00e7\u00e3o separada<\/li>\n\n\n\n<li>raiz\u00a0<code>\/<\/code>\u00a0quase ou totalmente cheia<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Exemplo de sa\u00edda inicial:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">df -h<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Sa\u00edda:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Filesystem                         Size  Used Avail Use% Mounted on<br>\/dev\/mapper\/ubuntu--vg-ubuntu--lv   12G   11G     0 100% \/<br>\/dev\/sda2                          2.0G  122M  1.7G   7% \/boot<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Nesse caso, o&nbsp;<code>\/<\/code>&nbsp;est\u00e1 dentro de um volume l\u00f3gico LVM, ent\u00e3o aumentar s\u00f3 o disco no VirtualBox n\u00e3o basta.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Vis\u00e3o geral do processo<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">O processo completo \u00e9 este:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>desligar a VM<\/li>\n\n\n\n<li>aumentar o tamanho do disco virtual no VirtualBox<\/li>\n\n\n\n<li>iniciar a VM<\/li>\n\n\n\n<li>confirmar qual parti\u00e7\u00e3o cont\u00e9m o LVM<\/li>\n\n\n\n<li>expandir essa parti\u00e7\u00e3o<\/li>\n\n\n\n<li>expandir o PV do LVM<\/li>\n\n\n\n<li>expandir o LV<\/li>\n\n\n\n<li>expandir o filesystem<\/li>\n\n\n\n<li>validar tudo no final<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">O comando\u00a0<code><a href=\"https:\/\/manpages.ubuntu.com\/manpages\/xenial\/en\/man1\/growpart.1.html\">growpart<\/a><\/code>\u00a0serve para estender a parti\u00e7\u00e3o at\u00e9 o espa\u00e7o livre dispon\u00edvel, o\u00a0<code>pvresize<\/code>\u00a0faz o LVM enxergar o novo tamanho da parti\u00e7\u00e3o, o\u00a0<code>lvextend<\/code>\u00a0aumenta o volume l\u00f3gico, e o\u00a0<code>resize2fs<\/code>\u00a0aumenta o filesystem ext2\/ext3\/ext4 para ocupar o espa\u00e7o dispon\u00edvel.\u00a0<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 0: fa\u00e7a backup ou snapshot<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Antes de mexer em parti\u00e7\u00f5es e LVM, fa\u00e7a um snapshot da VM.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Isso n\u00e3o \u00e9 obrigat\u00f3rio, mas \u00e9 a prote\u00e7\u00e3o mais importante caso algo saia errado.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 1: desligue a VM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A VM precisa estar desligada de verdade, n\u00e3o suspensa.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 2: aumente o disco virtual no VirtualBox<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">No host, aumente o VDI com&nbsp;<code>VBoxManage modifymedium<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Exemplo para passar o disco para&nbsp;<strong>50 GB<\/strong>:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">VBoxManage modifymedium \"\/caminho\/para\/DevVM.vdi\" --resize 51200<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O par\u00e2metro\u00a0<code>--resize<\/code>\u00a0usa megabytes. Ent\u00e3o\u00a0<code>51200<\/code>\u00a0significa 50 GB. O VirtualBox <a href=\"https:\/\/docs.oracle.com\/en\/virtualization\/virtualbox\/6.0\/user\/vboxmanage-modifymedium.html\">documenta<\/a> exatamente esse uso para redimensionar a imagem do disco virtual.\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Depois disso, o disco virtual cresceu, mas o Ubuntu ainda n\u00e3o vai usar o espa\u00e7o automaticamente.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 3: suba a VM e inspecione o layout do disco<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agora, dentro do Ubuntu, rode:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">lsblk<br>sudo fdisk -l \/dev\/sda<br>sudo pvs<br>sudo vgs<br>sudo lvs<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">O que voc\u00ea quer encontrar<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Voc\u00ea precisa descobrir:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>qual \u00e9 o disco principal, normalmente\u00a0<code>\/dev\/sda<\/code><\/li>\n\n\n\n<li>qual parti\u00e7\u00e3o cont\u00e9m o LVM, normalmente algo como\u00a0<code>\/dev\/sda3<\/code><\/li>\n\n\n\n<li>qual \u00e9 o nome do volume group e do logical volume<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Exemplo real:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS<br>sda                         8:0    0   50G  0 disk<br>\u251c\u2500sda1                      8:1    0    1M  0 part<br>\u251c\u2500sda2                      8:2    0    2G  0 part \/boot<br>\u2514\u2500sda3                      8:3    0   23G  0 part<br>  \u2514\u2500ubuntu--vg-ubuntu--lv 252:0    0 11.5G  0 lvm  \/<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Interpreta\u00e7\u00e3o:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>\/dev\/sda<\/code>\u00a0j\u00e1 est\u00e1 com 50G<\/li>\n\n\n\n<li><code>\/dev\/sda2<\/code>\u00a0\u00e9 o\u00a0<code>\/boot<\/code><\/li>\n\n\n\n<li><code>\/dev\/sda3<\/code>\u00a0\u00e9 a parti\u00e7\u00e3o que cont\u00e9m o LVM<\/li>\n\n\n\n<li>o LV raiz ainda est\u00e1 pequeno<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Outra sa\u00edda importante:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">PV         VG        Fmt  Attr PSize   PFree<br>\/dev\/sda3  ubuntu-vg lvm2 a--  &lt;23.00g 11.50g<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Aqui j\u00e1 fica claro que o LVM est\u00e1 em&nbsp;<code>\/dev\/sda3<\/code>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 4: instale o&nbsp;<code>growpart<\/code>&nbsp;se necess\u00e1rio<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">No Ubuntu, o&nbsp;<code>growpart<\/code>&nbsp;costuma vir no pacote&nbsp;<code>cloud-guest-utils<\/code>.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo apt update<br>sudo apt install -y cloud-guest-utils<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O&nbsp;<code>growpart<\/code>&nbsp;foi feito justamente para reescrever a tabela de parti\u00e7\u00e3o e fazer a parti\u00e7\u00e3o crescer at\u00e9 o fim do disco, ou at\u00e9 a pr\u00f3xima parti\u00e7\u00e3o.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Se ele j\u00e1 estiver instalado, voc\u00ea ver\u00e1 algo assim:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">cloud-guest-utils is already the newest version<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 5: expanda a parti\u00e7\u00e3o LVM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agora expanda a parti\u00e7\u00e3o que cont\u00e9m o LVM.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">No exemplo acima, a parti\u00e7\u00e3o \u00e9 a&nbsp;<strong>3<\/strong>, ent\u00e3o o comando fica:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo growpart \/dev\/sda 3<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Sa\u00edda esperada<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">CHANGED: partition=3 start=4198400 old: size=48228352 end=52426751 new: size=100659167 end=104857566<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Isso significa que a parti\u00e7\u00e3o 3 cresceu e agora ocupa o espa\u00e7o novo do disco.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Se voc\u00ea rodar&nbsp;<code>lsblk<\/code>&nbsp;depois, ver\u00e1 algo parecido com isto:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sda                         8:0    0   50G  0 disk<br>\u251c\u2500sda1                      8:1    0    1M  0 part<br>\u251c\u2500sda2                      8:2    0    2G  0 part \/boot<br>\u2514\u2500sda3                      8:3    0   48G  0 part<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 6: fa\u00e7a o LVM enxergar o novo tamanho da parti\u00e7\u00e3o<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agora o disco cresceu e a parti\u00e7\u00e3o cresceu, mas o LVM ainda precisa saber disso.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo pvresize \/dev\/sda3<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O&nbsp;<code>pvresize<\/code>&nbsp;redimensiona o physical volume para refletir o tamanho novo do dispositivo subjacente.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sa\u00edda esperada<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">Physical volume \"\/dev\/sda3\" changed<br>1 physical volume(s) resized or updated \/ 0 physical volume(s) not resized<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Depois disso, confirme com:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo vgs<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Exemplo:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">VG        #PV #LV #SN Attr   VSize   VFree<br>ubuntu-vg   1   1   0 wz--n- &lt;48.00g 11.50g<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Repare no&nbsp;<code>VFree<\/code>: agora j\u00e1 existe espa\u00e7o livre no volume group.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 7: expanda o volume l\u00f3gico raiz<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Agora \u00e9 hora de aumentar o LV onde est\u00e1 o&nbsp;<code>\/<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo lvextend -l +100%FREE -r \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O&nbsp;<code>lvextend<\/code>&nbsp;aumenta o logical volume, e a op\u00e7\u00e3o&nbsp;<code>-r<\/code>&nbsp;pede para tamb\u00e9m redimensionar o filesystem automaticamente.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sa\u00edda ideal<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Em muitos casos, voc\u00ea ver\u00e1 algo assim:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Size of logical volume ubuntu-vg\/ubuntu-lv changed from &lt;11.50 GiB to &lt;48.00 GiB.<br>File system ext4 found on ubuntu-vg\/ubuntu-lv mounted at \/.<br>Extending file system ext4...<br>Logical volume ubuntu-vg\/ubuntu-lv successfully resized.<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Mas pode acontecer este erro<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No meu caso real, apareceu isto:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Size of logical volume ubuntu-vg\/ubuntu-lv changed from &lt;11.50 GiB (2943 extents) to &lt;48.00 GiB (12287 extents).<br>File system ext4 found on ubuntu-vg\/ubuntu-lv mounted at \/.<br>Extending file system ext4 to &lt;48.00 GiB (51535413248 bytes) on ubuntu-vg\/ubuntu-lv...<br>\/usr\/libexec\/lvresize_fs_helper: execvp failed: No such file or directory<br>Failed to extend file system with lvresize_fs_helper.<br>File system extend error.<br>Logical volume ubuntu-vg\/ubuntu-lv successfully resized.<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Essa mensagem quer dizer:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>o\u00a0<strong>LV cresceu<\/strong><\/li>\n\n\n\n<li>mas o\u00a0<strong>filesystem n\u00e3o cresceu automaticamente<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Isso \u00e9 f\u00e1cil de confirmar:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">df -h<br>lsblk<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Se o&nbsp;<code>lsblk<\/code>&nbsp;mostrar&nbsp;<strong>48G<\/strong>, mas o&nbsp;<code>df -h<\/code>&nbsp;ainda mostrar&nbsp;<strong>12G<\/strong>&nbsp;no&nbsp;<code>\/<\/code>, ent\u00e3o o filesystem ainda precisa ser expandido manualmente.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Passo 8: se o&nbsp;<code>lvextend -r<\/code>&nbsp;falhar, rode&nbsp;<code>resize2fs<\/code><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Quando o filesystem for ext4, o&nbsp;<code>resize2fs<\/code>&nbsp;resolve.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo resize2fs \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O\u00a0<code>resize2fs<\/code>\u00a0\u00e9 a ferramenta padr\u00e3o para redimensionar filesystems ext2\/ext3\/ext4. A <a href=\"https:\/\/www.man7.org\/linux\/man-pages\/man8\/resize2fs.8.html\">documenta\u00e7\u00e3o<\/a> informa que ele pode expandir um filesystem montado, desde que o kernel suporte resize online, o que \u00e9 comum com ext4.\u00a0<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Resultado esperado<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Depois disso:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">df -h<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Sa\u00edda final esperada:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Filesystem                         Size  Used Avail Use% Mounted on<br>\/dev\/mapper\/ubuntu--vg-ubuntu--lv   48G   10G   36G  23% \/<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">E o&nbsp;<code>lsblk<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS<br>sda                         8:0    0   50G  0 disk<br>\u251c\u2500sda1                      8:1    0    1M  0 part<br>\u251c\u2500sda2                      8:2    0    2G  0 part \/boot<br>\u2514\u2500sda3                      8:3    0   48G  0 part<br>  \u2514\u2500ubuntu--vg-ubuntu--lv 252:0    0   48G  0 lvm  \/<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Nesse ponto, est\u00e1 tudo certo.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Como validar que deu certo<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Rode estes comandos:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">df -h \/<br>lsblk<br>sudo pvs<br>sudo vgs<br>sudo lvs<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Exemplo de estado final saud\u00e1vel<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">df -h \/<br>Filesystem                         Size  Used Avail Use% Mounted on<br>\/dev\/mapper\/ubuntu--vg-ubuntu--lv   48G   10G   36G  23% \/<\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo vgs<br>VG        #PV #LV #SN Attr   VSize   VFree<br>ubuntu-vg   1   1   0 wz--n- &lt;48.00g    0<\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo lvs<br>LV        VG        Attr       LSize<br>ubuntu-lv ubuntu-vg -wi-ao---- &lt;48.00g<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Interpreta\u00e7\u00e3o:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>disco aumentado com sucesso<\/li>\n\n\n\n<li>parti\u00e7\u00e3o aumentada com sucesso<\/li>\n\n\n\n<li>PV\/VG\/LV aumentados com sucesso<\/li>\n\n\n\n<li>filesystem aumentado com sucesso<\/li>\n\n\n\n<li>sistema pronto para uso<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Resumo r\u00e1pido dos comandos<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">No host<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">VBoxManage modifymedium \"\/caminho\/para\/DevVM.vdi\" --resize 51200<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Na VM Ubuntu<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">lsblk<br>sudo fdisk -l \/dev\/sda<br>sudo pvs<br>sudo vgs<br>sudo lvssudo apt update<br>sudo apt install -y cloud-guest-utilssudo growpart \/dev\/sda 3<br>sudo pvresize \/dev\/sda3<br>sudo lvextend -l +100%FREE -r \/dev\/mapper\/ubuntu--vg-ubuntu--lvdf -h<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Se o filesystem n\u00e3o crescer sozinho<\/h3>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo resize2fs \/dev\/mapper\/ubuntu--vg-ubuntu--lv<br>df -h<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Erros comuns e o que significam<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1.&nbsp;<code>df -h<\/code>&nbsp;continua mostrando o tamanho antigo<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Isso normalmente significa que o LV cresceu, mas o filesystem n\u00e3o.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Corre\u00e7\u00e3o:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo resize2fs \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">O&nbsp;<code>resize2fs<\/code>&nbsp;\u00e9 justamente a ferramenta usada para fazer o filesystem ext4 ocupar o novo tamanho dispon\u00edvel.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2.&nbsp;<code>GPT PMBR size mismatch<\/code><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Esse aviso pode aparecer depois que o VDI \u00e9 aumentado, antes de a tabela de parti\u00e7\u00e3o ser regravada.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Em geral, depois do&nbsp;<code>growpart<\/code>, isso deixa de ser problema pr\u00e1tico, porque a parti\u00e7\u00e3o \u00e9 reescrita com o novo limite do disco.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Falta espa\u00e7o at\u00e9 para rodar os comandos<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Se o&nbsp;<code>\/<\/code>&nbsp;estiver em 100%, voc\u00ea pode limpar algumas coisas antes:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo apt clean<br>sudo journalctl --vacuum-time=3d<br>rm -rf ~\/.cache\/*<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclus\u00e3o<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Aumentar o disco de uma VM Ubuntu no VirtualBox envolve duas partes:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>aumentar a\u00a0<strong>imagem do disco<\/strong>\u00a0no VirtualBox<\/li>\n\n\n\n<li>aumentar\u00a0<strong>parti\u00e7\u00e3o + LVM + filesystem<\/strong>\u00a0dentro do Ubuntu<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">O ponto mais importante \u00e9 este:&nbsp;<strong>crescer o VDI n\u00e3o aumenta automaticamente o&nbsp;<code>\/<\/code><\/strong>. Voc\u00ea ainda precisa expandir a parti\u00e7\u00e3o, o PV, o LV e, se necess\u00e1rio, o filesystem. O&nbsp;<code>growpart<\/code>, o&nbsp;<code>pvresize<\/code>, o&nbsp;<code>lvextend<\/code>&nbsp;e o&nbsp;<code>resize2fs<\/code>&nbsp;s\u00e3o as ferramentas certas para isso.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Se voc\u00ea aumentou o disco virtual no VirtualBox, mas o Ubuntu continua mostrando pouco espa\u00e7o livre, este guia resolve o problema completo. Esse cen\u00e1rio \u00e9 muito comum quando a VM usa\u00a0LVM: o disco virtual cresce, mas a parti\u00e7\u00e3o, o volume f\u00edsico, o volume group, o volume l\u00f3gico e o filesystem\u00a0n\u00e3o crescem sozinhos. O VirtualBox expande&#8230;<\/p>\n","protected":false},"author":1,"featured_media":313,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[45],"tags":[84,81,82],"class_list":["post-290","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dicas","tag-disk-resize","tag-linux","tag-virtualbox"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/www.bernabauer.com\/blog\/wp-content\/uploads\/2026\/05\/linux-terminal-virtualbox.jpg","_links":{"self":[{"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/posts\/290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/comments?post=290"}],"version-history":[{"count":1,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/posts\/290\/revisions"}],"predecessor-version":[{"id":291,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/posts\/290\/revisions\/291"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/media\/313"}],"wp:attachment":[{"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/media?parent=290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/categories?post=290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bernabauer.com\/blog\/wp-json\/wp\/v2\/tags?post=290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}