You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Out of curiosity, I tried to run the latest ARM64 release of Rustic, inside an Ubuntu chroot, on my Android phone.
It seems that I was able to create an archive, in an existing Restic repository, without issues,
but when I attempted to add /proc, as a stress test (/proc/kcore usually either ends up being read, for a very long time, or gets handled in an optimised manner, given its size, by various tools).
Version information, for Ubuntu, and Android Linux kernel:
First of all, thanks for using rustic and for reporting this bug.
A first look at the report file shows a panic inside std::io which makes me think (without being certain) that the bug that happened is outside of rustic's range.
nardoor
added
C-bug
Category: Something isn't working as expected
A-cli
Area: `rustic` command line interface
O-unix
Operating system: Unix-like
and removed
S-triage
Status: Waiting for a maintainer to triage this issue/PR
labels
Nov 17, 2024
Out of curiosity, I tried to run the latest ARM64 release of Rustic, inside an Ubuntu chroot, on my Android phone.
It seems that I was able to create an archive, in an existing Restic repository, without issues,
but when I attempted to add /proc, as a stress test (/proc/kcore usually either ends up being read, for a very long time, or gets handled in an optimised manner, given its size, by various tools).
Version information, for Ubuntu, and Android Linux kernel:
Attaching the report file generated, after processing about 100GB of data, before it crashed:
report-55e94011-5b01-4ad7-8dd1-bd92a4cb3c65.toml.gz
The text was updated successfully, but these errors were encountered: