[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] Out of disk space




On 05/24/2018 07:58 PM, Rares Vernica wrote:
> Hello,
> 
> I have a recently installed Atomic CentOS bare-metal server. I have about 3TB of physical disk available on it:
> 
> # pvdisplay
>   --- Physical volume ---
>   PV Name               /dev/sda2
>   VG Name               cah_b
>   PV Size               <931.22 GiB / not usable 4.00 MiB
>   Allocatable           yes
>   PE Size               4.00 MiB
>   Total PE              238391
>   Free PE               189058
>   Allocated PE          49333
>   PV UUID               pkZPnK-eSj2-1KQD-nFMf-X7Wn-F0hm-A20ESN
>   
>   --- Physical volume ---
>   PV Name               /dev/sdb1
>   VG Name               cah_b
>   PV Size               931.51 GiB / not usable 4.00 MiB
>   Allocatable           yes (but full)
>   PE Size               4.00 MiB
>   Total PE              238466
>   Free PE               0
>   Allocated PE          238466
>   PV UUID               uPNaDO-MfpL-gyKw-q5pz-BBMR-2SLx-jGXK9r
>   
>   --- Physical volume ---
>   PV Name               /dev/sdc1
>   VG Name               cah_b
>   PV Size               931.51 GiB / not usable 4.00 MiB
>   Allocatable           yes
>   PE Size               4.00 MiB
>   Total PE              238466
>   Free PE               238466
>   Allocated PE          0
>   PV UUID               A4J2or-ly4m-OFVY-VBpl-I28h-qioF-i0CXcI
> 
> With the default installation, I just started Cockpit and Docker Registry and ran out of disk space on root:
> 
> # df -h
> Filesystem                    Size  Used Avail Use% Mounted on
> /dev/mapper/cah_b-root  3.0G  3.0G  1.6M 100% /
> devtmpfs                       16G     0   16G   0% /dev
> tmpfs                          16G     0   16G   0% /dev/shm
> tmpfs                          16G  1.2M   16G   1% /run
> tmpfs                          16G     0   16G   0% /sys/fs/cgroup
> /dev/sda1                     297M  167M  130M  57% /boot
> tmpfs                         3.2G     0  3.2G   0% /run/user/0
> 

yes. With overlay2 as default if you don't give it any other options all the container
disk usage will go in the root filesystem

> What is the recommended way to grow the space available on root?


You can use `lvresize` for this. Please look at the man page [1] first
but something like this should work:

lvresize cah_b/root --resizefs --size=+30G 

Dusty

[1] https://linux.die.net/man/8/lvresize


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]