Re: no space left on device

[Ludovic Courtès]

Catonano <address@hidden> skribis:

> in trying to build a vm image that runs core-updates, I run into this error
>
> ...
> ...
> ...
> `/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/ja/LC_MESSAGES/libgpg-error.mo'
> ->
> `/fs/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/ja/LC_MESSAGES/libgpg-error.mo'
> `/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/de/LC_MESSAGES/libgpg-error.mo'
> ->
> `/fs/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/de/LC_MESSAGES/libgpg-error.mo'
> `/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/pl/LC_MESSAGES/libgpg-error.mo'
> ->
> `/fs/gnu/store/j92kxc1l8h879cc4ss1gbhsq73ddnbsg-libgpg-error-1.26/share/locale/pl/LC_MESSAGES/libgpg-error.mo'
> ERROR: In procedure copy-file:
> ERROR: In procedure copy-file: No space left on device
>
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> [  136.307896] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000000
> [  136.307896]
> [  136.309002] CPU: 0 PID: 1 Comm: init Not tainted 4.10.5-gnu #1
> [  136.309722] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
> rel-1.10.1-0-g8891697-prebuilt.qemu-project.org 04/01/2014
> [  136.311114] Call Trace:
> [  136.311651]  dump_stack+0x63/0x90
> [  136.312101]  panic+0xe4/0x22d
> [  136.312491]  do_exit+0xb21/0xb30
> [  136.312888]  ? wake_up_state+0x10/0x20
> [  136.313279]  do_group_exit+0x43/0xb0
> [  136.313674]  SyS_exit_group+0x14/0x20
> [  136.314077]  entry_SYSCALL_64_fastpath+0x1e/0xad
> [  136.314580] RIP: 0033:0x5e6b98
> [  136.314973] RSP: 002b:00007ffc5ac95d78 EFLAGS: 00000246 ORIG_RAX:
> 00000000000000e7
> [  136.316217] RAX: ffffffffffffffda RBX: 0000000000000001 RCX:
> 00000000005e6b98
> [  136.317519] RDX: 0000000000000000 RSI: 000000000000003c RDI:
> 0000000000000000
> [  136.318405] RBP: 00000000007ef4d0 R08: 00000000000000e7 R09:
> ffffffffffffffc8
> [  136.319211] R10: 0000000000000000 R11: 0000000000000246 R12:
> 00000000004cd850
> [  136.320041] R13: 0000000000a7f020 R14: 0000000001c73e60 R15:
> 0000000000000001
> [  136.321284] Kernel Offset: 0x27000000 from 0xffffffff81000000
> (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
> [  136.322758] ---[ end Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000000
> [  136.322758]
>
>
> I don't understand: is this happening in my host ? Or is this happening
> inside the Qemu machine ?

Most likely inside the QEMU machine.

If you’re using ‘guix system vm-image’, you’ll have to pass

   --image-size=SIZE

where SIZE is the appropriate image size.  Failing to do that, the
command creates a small disk image and things don’t fit in it, hence
this error.

To determine what an appropriate size might be, you can do:

  guix size $(guix system build config.scm)

and then add maybe 10% to that (to account for the space taken by file
system metadata, the partition table, etc.)

That said, ‘guix system vm’ (not ‘vm-image’) should work out-of-the-box,
without having to specify --image-size.

HTH!

Ludo’.