English
« Back to projectatomic.io
Ask Your Question
0

can't upgrade - no space left on device

asked 2016-11-07 23:08:13 +0000

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

Hi, I cannot upgrade my atomic instance, getting "error: No space left on device". Now sadly I'm still a Linux noob in general and with LVM especially so I have no idea how to fix this. I DO know however that I have still space left somewhere on that disk.
Normally I would just mount /dev/sda2 on / but I suppose that /dev/sda2 is being used by atomic for the docker images. (Also I'm getting 'mount: unknown filesystem type 'LVM2_member'')

df output

-bash-4.2# df
Filesystem           1K-blocks    Used Available Use% Mounted on
/dev/mapper/cah-root   3135488 3135448        40 100% /
devtmpfs               1913184       0   1913184   0% /dev
tmpfs                  1932716       0   1932716   0% /dev/shm
tmpfs                  1932716   25136   1907580   2% /run
tmpfs                  1932716       0   1932716   0% /sys/fs/cgroup
/dev/sda1               303788   89600    214188  30% /boot
tmpfs                   386544       0    386544   0% /run/user/0

/dev/sda2 does not even show up here, shouldn't it do that?

Can you please help me?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-11-08 15:03:13 +0000

zachar gravatar image

I just run into the same issue. Here is the way how I fixed it:

step1: Verify that you have enough space in the volume group (VFree):

-bash-4.2# vgs
VG     #PV #LV #SN Attr   VSize VFree
cah   1   3   0 wz--n- 9.70g 3.41g

step2: increase the size of the logical volume of root with 1G:

-bash-4.2# lvextend -L+1G /dev/cah/root 
  Size of logical volume cah/root changed from 3.00 GiB (768 extents) to 4.00 GiB (1024 extents).
  Logical volume root successfully resized.

step3: grow the root filesystem:

-bash-4.2#  xfs_growfs /
meta-data=/dev/mapper/rhelah-root isize=256    agcount=4, agsize=196608 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0        finobt=0
data     =                       bsize=4096   blocks=786432, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 786432 to 1048576
-bash-4.2# df -hl
Filesystem               Size  Used Avail Use% Mounted on
/dev/mapper/rhelah-root  4.0G  3.0G  1.1G  75% /
devtmpfs                 982M     0  982M   0% /dev
tmpfs                   1001M     0 1001M   0% /dev/shm
tmpfs                   1001M  420K 1001M   1% /run
tmpfs                   1001M     0 1001M   0% /sys/fs/cgroup
/dev/vda1                297M  111M  187M  38% /boot
tmpfs                    201M     0  201M   0% /run/user/0
-bash-4.2#

I hope this helps, Balazs

edit flag offensive delete link more

Comments

The problem is in the default installation of Atomic. It creates a 3GB logical volume (LV) for the system, but doesn't configure other LVs for the "data"/containers. After installation, there should still be space left on the volume group. Create a new LV and set it as storage for your containers.

huygens ( 2016-12-14 12:31:10 +0000 )edit

See this resource on the project documentation pages: http://www.projectatomic.io/docs/docker-storage-recommendation/

huygens ( 2016-12-14 12:31:39 +0000 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Stats

Asked: 2016-11-07 23:08:13 +0000

Seen: 346 times

Last updated: Nov 08 '16