* no space left on device
@ 2017-03-30 12:27 Catonano
2017-03-30 12:32 ` ng0
2017-03-30 14:11 ` Ludovic Courtès
0 siblings, 2 replies; 6+ messages in thread
From: Catonano @ 2017-03-30 12:27 UTC (permalink / raw
To: help-guix
[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]
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 ?
On my host I run df -h and I get
~$ df -h
File system Dim. Usati Dispon. Uso% Montato su
none 3,7G 0 3,7G 0% /dev
/dev/sda5 99G 25G 69G 27% /
/dev/sda1 269M 11M 241M 5% /boot
/dev/sda6 129G 15G 108G 12% /home
""Dispon" means available
Montato su -> Mounted on
So /tmp is in the root partiton ( /dev/sda5 ) and I'd say there's quite a
bit of space available
Where am I ?
Thanks
[-- Attachment #2: Type: text/html, Size: 3422 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: no space left on device
2017-03-30 12:27 no space left on device Catonano
@ 2017-03-30 12:32 ` ng0
2017-03-30 12:46 ` Catonano
2017-03-30 14:11 ` Ludovic Courtès
1 sibling, 1 reply; 6+ messages in thread
From: ng0 @ 2017-03-30 12:32 UTC (permalink / raw
To: Catonano; +Cc: help-guix
Catonano transcribed 6.8K bytes:
> 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 ?
Is this with a plain qemu machine or one you spawn with "guix system vm"?
"guix system vm" machines are in /gnu/store/ and you first have to copy
them out of there to be able to write in them.
> On my host I run df -h and I get
>
>
> ~$ df -h
> File system Dim. Usati Dispon. Uso% Montato su
> none 3,7G 0 3,7G 0% /dev
> /dev/sda5 99G 25G 69G 27% /
> /dev/sda1 269M 11M 241M 5% /boot
> /dev/sda6 129G 15G 108G 12% /home
>
> ""Dispon" means available
> Montato su -> Mounted on
>
> So /tmp is in the root partiton ( /dev/sda5 ) and I'd say there's quite a
> bit of space available
>
> Where am I ?
>
> Thanks
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: no space left on device
2017-03-30 12:32 ` ng0
@ 2017-03-30 12:46 ` Catonano
2017-03-30 13:39 ` Catonano
0 siblings, 1 reply; 6+ messages in thread
From: Catonano @ 2017-03-30 12:46 UTC (permalink / raw
To: Catonano, help-guix
[-- Attachment #1: Type: text/plain, Size: 3100 bytes --]
2017-03-30 14:32 GMT+02:00 ng0 <contact.ng0@cryptolab.net>:
> Catonano transcribed 6.8K bytes:
> > 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 ?
>
> Is this with a plain qemu machine or one you spawn with "guix system vm"?
> "guix system vm" machines are in /gnu/store/ and you first have to copy
> them out of there to be able to write in them.
>
>
This is with
guix system vm-image /etc/config.scm
As far as I understand, I didn't even attempted to run the machine. I was
just building the image
Does this clarify ?
Thanks
[-- Attachment #2: Type: text/html, Size: 4240 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: no space left on device
2017-03-30 12:46 ` Catonano
@ 2017-03-30 13:39 ` Catonano
0 siblings, 0 replies; 6+ messages in thread
From: Catonano @ 2017-03-30 13:39 UTC (permalink / raw
To: help-guix
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
2017-03-30 14:46 GMT+02:00 Catonano <catonano@gmail.com>:
Is this with a plain qemu machine or one you spawn with "guix system vm"?
>> "guix system vm" machines are in /gnu/store/ and you first have to copy
>> them out of there to be able to write in them.
>>
>>
>
>
Noow that you make me think about it: the /etc/config.scm file describes a
layout with 3 partitions, root, boot and home.
I suppose those won't be reorganized automagically to be made sutable to my
vm ?
Mmm
What could be a sensible layout for this vm ?
> This is with
>
> guix system vm-image /etc/config.scm
>
> As far as I understand, I didn't even attempted to run the machine. I was
> just building the image
>
> Does this clarify ?
>
> Thanks
>
[-- Attachment #2: Type: text/html, Size: 1877 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: no space left on device
2017-03-30 12:27 no space left on device Catonano
2017-03-30 12:32 ` ng0
@ 2017-03-30 14:11 ` Ludovic Courtès
2017-03-30 14:31 ` Catonano
1 sibling, 1 reply; 6+ messages in thread
From: Ludovic Courtès @ 2017-03-30 14:11 UTC (permalink / raw
To: Catonano; +Cc: help-guix
Catonano <catonano@gmail.com> 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’.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: no space left on device
2017-03-30 14:11 ` Ludovic Courtès
@ 2017-03-30 14:31 ` Catonano
0 siblings, 0 replies; 6+ messages in thread
From: Catonano @ 2017-03-30 14:31 UTC (permalink / raw
To: Ludovic Courtès; +Cc: help-guix
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
2017-03-30 16:11 GMT+02:00 Ludovic Courtès <ludo@gnu.org
>
> > 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’.
>
Thank you Ludo, system vm made it quickly
[-- Attachment #2: Type: text/html, Size: 1363 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-03-30 14:31 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-30 12:27 no space left on device Catonano
2017-03-30 12:32 ` ng0
2017-03-30 12:46 ` Catonano
2017-03-30 13:39 ` Catonano
2017-03-30 14:11 ` Ludovic Courtès
2017-03-30 14:31 ` Catonano
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.