target/lorri

Lorri Crash report

Gerschtli opened this issue · 2 comments

Describe the bug
Did nothing special and despite the errors everything is working fine again

To Reproduce
Steps to reproduce the behavior:

  1. ...
  2. ...
  3. ...

Expected behavior

No crashes :D

Metadata

name = 'lorri'
operating_system = 'unix:Ubuntu'
crate_version = '1.2.0'
explanation = '''
Panic occurred in file 'src/build_loop.rs' at line 184
'''
cause = '''
Unrecoverable error:
Io {
    msg: "Error { kind: Io(Os { code: 28, kind: Other, message: \"No space left on device\" }), paths: [] }",
}'''
method = 'Panic'
backtrace = '''

   0: 0x5624a25333ce - std::sys_common::backtrace::__rust_begin_short_backtrace::hcebe9c3cdd640ad4
   1: 0x5624a256da1a - core::ops::function::FnOnce::call_once{{vtable.shim}}::h2f41e3c70c1a09f1
   2: 0x5624a2722cca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
   3: 0x7f7e904faead - start_thread
   4: 0x7f7e90411d2f - __GI___clone
   5:        0x0 - <unknown>'''
name = 'lorri'
operating_system = 'unix:Ubuntu'
crate_version = '1.2.0'
explanation = '''
Panic occurred in file 'src/ops/watch.rs' at line 58
'''
cause = 'called `Result::unwrap()` on an `Err` value: Any'
method = 'Panic'
backtrace = '''

   0: 0x55ec713dbdce - lorri::main::h085cbcd6c2845fcb
   1: 0x55ec713e7f63 - std::rt::lang_start::{{closure}}::hf1bbaa013b752c09
   2: 0x55ec7163ebf7 - std::rt::lang_start_internal::h7d1b27a1580794aa
   3: 0x55ec713dd2e2 - main
   4: 0x7f107e942c7d - __libc_start_main
   5: 0x55ec713d41fa - _start
   6:        0x0 - <unknown>'''
name = 'lorri'
operating_system = 'unix:Ubuntu'
crate_version = '1.2.0'
explanation = '''
Panic occurred in file 'src/build_loop.rs' at line 184
'''
cause = '''
Unrecoverable error:
Io {
    msg: "Error { kind: Io(Os { code: 28, kind: Other, message: \"No space left on device\" }), paths: [] }",
}'''
method = 'Panic'
backtrace = '''

   0: 0x55ec714523ce - std::sys_common::backtrace::__rust_begin_short_backtrace::hcebe9c3cdd640ad4
   1: 0x55ec7148ca1a - core::ops::function::FnOnce::call_once{{vtable.shim}}::h2f41e3c70c1a09f1
   2: 0x55ec71641cca - std::sys::unix::thread::Thread::new::thread_start::h2dd53bf76d714ab0
   3: 0x7f107eaffead - start_thread
   4: 0x7f107ea16d2f - __GI___clone
   5:        0x0 - <unknown>'''
$ lorri info --shell-file shell.nix 
lorri version: 1.2
GC roots exist, shell_gc_root: "/home/tobias/.cache/lorri/gc_roots/551ed538d336a1646f7ded6ca4c37901/gc_root/shell_gc_root"
$ uname -a
Linux radon 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 GNU/Linux

Same problem here when running lorri watch. Which directories is lorri using (possibly when running nix).

I'm watching my tmpfss and they do not seem to be used while nix is building:

Every 2,0s: df -h | grep tmp                                                               pamperito: Wed Nov 18 18:21:43 2020

tmpfs           1,6G  4,1M  1,6G   1% /run
tmpfs           7,7G  196M  7,5G   3% /dev/shm
tmpfs           5,0M  4,0K  5,0M   1% /run/lock
tmpfs           7,7G     0  7,7G   0% /sys/fs/cgroup
tmpfs           4,0G   28K  4,0G   1% /run/user/120
tmpfs           4,0G  6,6M  4,0G   1% /run/user/1001

My root has 47 G available, and I even tried setting the TMPDIR to a folder inside / with the same results.

After allocating 16G of runtime directory, and freeing 150G from my / I still had the same problem. I upgraded to the latest lorri version:

lorri self-upgrade

and this solved the problem.