2011/9/26 Matthew McClintock <[email protected]>: > Have you checked your rootfs itself to see how much free space is > left? You could mount it in loopback on your build machine to check. > > There are some vars within poky that determine the rootfs size, grep > for IMAGE_ROOTFS_SIZE.
I'm actually seeing a similiar issue at the moment: Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory bootlogd. tar: can't open '/etc/dev.tar': No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 40: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 52: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No space left on device /etc/rcS.d/S37populate-volatile.sh: line 25: /etc/volatile.cache: No space left on device Configuring network interfaces... ADDRCONF(NETDEV_UP): eth0: link is not ready udhcpc (v1.18.5) started Sending discover... Sending discover... Sending discover... No lease, failing done. INIT: Entering runlevel: 5postin -M _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
