On Mon, 2019-03-11 at 13:47 -0400, Jeremiah C. Foster wrote:
On Mon, 2019-03-11 at 13:39 -0400, Jeremiah C. Foster wrote:
On Mon, 2019-03-11 at 18:10 +0100, Matthias Klumpp wrote:
Am Mo., 11. März 2019 um 15:06 Uhr schrieb Jeremiah C. Foster jeremiah.foster@puri.sm:
[...] Using the above process filled up my disk. For some reason the pagemap file grew to 77 Gigs and on that partition it ran out of space.
-r-------- 1 root root 77G Mar 8 16:37 pagemap
I'll try on another (slightly larger) partition. How much disk space should one have for this? 77 Gigs seems like an awful lot of space for an image. All the source code for a image and yocto tooling in comparison comes to about 60 Gigs or so.
That's odd... The whole process defbitely works if you have much less then 4GB of disk space, and I think our current autobuilder has 30GB. What data was written to where, can you find that out?
To follow up, I ran the command again in the container. This is the output;
[2019-03-13 19:17:11] lb bootstrap_cache save P: Saving bootstrap stage to cache... cp: error reading 'chroot/proc/1/attr/current': Invalid argument cp: error reading 'chroot/proc/1/attr/prev': Invalid argument cp: error reading 'chroot/proc/1/attr/exec': Invalid argument cp: error reading 'chroot/proc/1/attr/fscreate': Invalid argument cp: error reading 'chroot/proc/1/attr/keycreate': Invalid argument cp: error reading 'chroot/proc/1/attr/sockcreate': Invalid argument cp: error reading 'chroot/proc/1/task/1/mem': Input/output error cp: error reading 'chroot/proc/1/task/1/clear_refs': Invalid argument
Then lb just writes the bootstrap_cache to pagemap until disk fills up.
Cheers,
jeremiah