Backing up Docker Desktop Volume via Windows network share runs forever

[douglasparker]

Backing up a Docker Desktop Volume (Windows Share) results in the backup going on forever and not working as expected.

Backup Directory: \\wsl.localhost\docker-desktop-data\data\docker\volumes
Output:

[00:56:29] backing up...                  ████████████████████████████████████████ 458.17 GiB/62.55 GiB  127.48 MiB/s (ETA -)

Rclone had this same problem, but disabling preallocation of disk space fixed it. This will not fix rustic however, even when using the rclone backend with the environmental variable set.

[aawsome]

@douglasparker Can you please give more information? What backend are you using? Can you give the full output of the backup command, maybe using higher --log-level?

What was the rclone issue and why do you thing this disabling of preallocation fixed it? Note that rustic doesn't do any kind of such preallocation...

[douglasparker]

@douglasparker Can you please give more information? What backend are you using? Can you give the full output of the backup command, maybe using higher --log-level?

I was using the rclone backend with S3 compatible storage.

I couldn't test with opendal because of #1162

Unfortunately, I did not like some of the tradeoffs with Docker Desktop so I no longer have any of that enabled for my workstation so I cannot get better logging for you.

What was the rclone issue and why do you thing this disabling of preallocation fixed it? Note that rustic doesn't do any kind of such preallocation...

I believe the maintainer of rclone thinks that the WSL driver is implementing preallocations wrong. See his reply here: https://forum.rclone.org/t/rclone-copy-fails-to-wsl2-dos-copy-works/38351/4

I have no idea if these issues are related- I just know I had a similar with rclone. Copy and sync went on forever and similarly had the progress in GB being way higher than the total transfer size. Also, files were corrupted with rclone for the destination. Disabling preallocations in rclone fixed that issue for me.

[aawsome]

As this cannot be reproduced I can only give some hints about how to get more information:

• Use rustic --log-level=debug or --log-level=trace to get more information from rustic.
• Set RCLONE_VERBOSE=2 or RCLONE_VERBOSE=3 to get more output from rclone. Note that rustic also outputs such rclone output.