0
rufik

No space left (loop) while building image

Recommended Posts

I've just tried to build my custom image for OPI 2 but got into some trouble with space:

 

Spoiler

[ o.k. ] Preparing image file for rootfs [ orangepi2 xenial ]
[ o.k. ] Current rootfs size [ 753 MiB ]
[ o.k. ] Creating blank image for rootfs [ 872 MiB ]
 872MiB [42,5MiB/s] [===========================================================================================================================================>] 100%
[ o.k. ] Creating partitions [ root: ext4 ]
[ .... ] Creating rootfs [ ext4 ]
[ .... ] Copying files to root directory 
        657.56M  99%   25.52MB/s    0:00:24 (xfr#44298, to-chk=4/56213)   
rsync: mkstemp "/home/rufik/workspace/armbian/.tmp/mount-next-orangepi2-xenial-no/var/lib/dpkg/info/.libtext-wrapi18n-perl.list.s6O3ub" failed: No space left on device (28)
rsync: mkstemp "/home/rufik/workspace/armbian/.tmp/mount-next-orangepi2-xenial-no/var/lib/dpkg/info/.libtext-wrapi18n-perl.md5sums.rlQNhJ" failed: No space left on device (28)
[... a lot of files failures...]
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]
[ o.k. ] Free space: [ SD card ]
Filesystem      Size  Used Avail Use% Mounted on
udev            1,9G     0  1,9G   0% /dev
tmpfs           395M  1,3M  393M   1% /run
/dev/sda2        49G   22G   25G  48% /
tmpfs           2,0G     0  2,0G   0% /dev/shm
tmpfs           5,0M     0  5,0M   0% /run/lock
tmpfs           2,0G     0  2,0G   0% /sys/fs/cgroup
/dev/loop0       87M   87M     0 100% /snap/core/4917
/dev/loop1      3,8M  3,8M     0 100% /snap/gnome-system-monitor/51
/dev/loop2       21M   21M     0 100% /snap/gnome-logs/25
/dev/loop3      2,4M  2,4M     0 100% /snap/gnome-calculator/180
/dev/loop4       13M   13M     0 100% /snap/gnome-characters/103
/dev/loop5      141M  141M     0 100% /snap/gnome-3-26-1604/70
/dev/loop6      141M  141M     0 100% /snap/gnome-3-26-1604/59
/dev/loop7      1,7M  1,7M     0 100% /snap/gnome-calculator/154
/dev/loop8      3,4M  3,4M     0 100% /snap/gnome-system-monitor/36
/dev/loop9       13M   13M     0 100% /snap/gnome-characters/69
/dev/loop10      15M   15M     0 100% /snap/gnome-logs/37
/dev/loop11      87M   87M     0 100% /snap/core/4486
/dev/sda1       511M  4,7M  507M   1% /boot/efi
Temp            230G  181G   50G  79% /media/sf_Temp
tmpfs           395M   40K  395M   1% /run/user/1000
tmpfs           2,6G  753M  1,9G  29% /home/rufik/workspace/armbian/.tmp/rootfs-next-orangepi2-xenial-no
/dev/loop12p1   839M  752M   54M  94% /home/rufik/workspace/armbian/.tmp/mount-next-orangepi2-xenial-no
[ o.k. ] Writing U-boot bootloader [ /dev/loop12 ]
[ o.k. ] Done building [ /home/rufik/workspace/armbian/output/images/Armbian_5.54_Orangepi2_Ubuntu_xenial_next_4.17.11.img ]
[ o.k. ] Runtime [ 50 min ]

 

 

I'm not really short of root fs space. It looks like /dev/loop12p1 lacks of free space. Why? Should I adjust this loop device size somehow?

I'm building on Ubuntu 18.04.

Share this post


Link to post
Share on other sites
3 hours ago, Igor said:


Are you adding/changing anything?

 

Yup, midnight commander via apt-get :)

 

2 hours ago, Igor said:

Retry now.

 

Thanks, I just found this place to be adjusted.

Share this post


Link to post
Share on other sites

Is it O.K. now? 
I didn't test directly your value (1.20), I set it to 2.0 because of my customization I'm preparing - it works fine. I suppose it should be OK.

Share this post


Link to post
Share on other sites
2 minutes ago, rufik said:

I didn't test directly your value (1.20), I set it to 2.0 because of my customization I'm preparing - it works fine. I suppose it should be OK.


OK. BTW. 2 is overkill :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
0