-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restic stalling on /etc
under WSL1
#4730
Comments
Stack trace (including terminal output until `pkill -ABRT restic`
|
Thanks a lot! I requested the stack trace on Mastodon (because I was curious), at least one Goroutine hangs in an IO wait (stack trace formatted with
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Output of
restic version
restic 0.16.4 compiled with go1.21.6 on linux/amd64
What backend/service did you use to store the repository?
rclone over SSH, with the remote running
rclone serve restic --stdio
, but it doesn't work via SFTP or using a local repo either.Problem description / Steps to reproduce
Running under WSL1 in Windows 10,
restic snapshot
apparently stops reading files very early in the backup, unless I exclude/dev
. Terminal output will still update, but other than that, all activity seems to stall. CPU usage stays at 0 to 3 %, memory usage stays constant. The issue occurs on local and remote repositories, and adding--exclude /dev
fixes it.My command line (as root) is
restic backup --dry-run --compression=auto --exclude-caches --exclude-file=/etc/restic/default.exclude --exclude-file=/etc/restic/network.exclude --exclude-file=/etc/restic/scy.exclude --password-file=/etc/restic/REDACTED.key --repo=sftp:HOST_REDACTED:PATH_REDACTED --tag=profile:system --verbose=2 /
, usually launched via resticprofile, but the issue occurs also when running standalone. And yes, this is a dry run, but it also occurs in a real run.Actually I don't mind simply excluding
/dev
as a workaround, but @fd0 asked me on Mastodon to create a bug report with a stack trace, so here we are 😉 I'll have to post the stack trace in a follow-up comment though because else this text is over 64 KiB and GitHub won't let me post it …Expected behavior
restic creates a backup.
Actual behavior
restic stops creating a backup and apparently does nothing except for updating the terminal.
Do you have any idea what may have caused this?
WSL1 has all sorts of quirks; there's a reason it's no longer supported by Microsoft.
I assume there's something special in
/dev
that restic chokes on. Is there a way for me to see the path where it gets stuck? Note that it stops after three files in/bin
(there are more than three in the directory 😉), so it looks to me as if not actually reading/chunking the files is the issue, but listing them.Indeed, when I add
--no-scan
, it stalls later:Looks as if files are being read slightly out of order, for example
/boot
and/bin
and/etc
intermix with each other here, and this is with--read-concurrency 1
.Did restic help you today? Did it make you happy in any way?
Yes! restic is easy to install and configure while still being very powerful. I like the tags and ETA features and the flexibility that comes with using rclone as a destination.
The text was updated successfully, but these errors were encountered: