-
Notifications
You must be signed in to change notification settings - Fork 1.7k
A Dokany mounted filesystem can not be backed up #3594
Description
Output of restic version
restic 0.12.1 compiled with go1.16.6 on windows/amd64
How did you run restic exactly?
PS C:\Users\Chris\Robust\Backup> restic.exe --repo '\\ccnas\Backup\Robust\restic\' backup 'C:\Users\Chris\Robust\Client\UofT\' -v
open repository
enter password for repository:
repository d847d773 opened successfully, password is correct
lock repository
load index files
using parent snapshot 28c247f8
start scan on [C:\Users\Chris\Robust\Client\UofT\]
start backup on [C:\Users\Chris\Robust\Client\UofT\]
scan finished in 1.012s: 0 files, 0 B
error: NodeFromFileInfo: Readlink: readlink \\?\C:\Users\Chris\Robust\Client\UofT: The system cannot find the file specified.
Files: 0 new, 0 changed, 0 unmodified
Dirs: 0 new, 0 changed, 5 unmodified
Data Blobs: 0 new
Tree Blobs: 0 new
Added to the repo: 0 B
processed 0 files, 0 B in 0:01
snapshot 255e9b8c saved
Warning: at least one source file could not be read
PS C:\Users\Chris\Robust\Backup> dir 'C:\Users\Chris\Robust\Client\UofT\'
Directory: C:\Users\Chris\Robust\Client\UofT
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 2021-12-10 5:35 PM Case
------ 2021-12-10 5:35 PM 6210 UofT.bmp
------ 2021-12-10 5:35 PM 1541 IMG_0019.JPG
------ 2021-12-10 5:35 PM 21504 Notes.xls
------ 2021-12-10 5:35 PM 34304 t.doc
PS C:\Users\Chris\Robust\Backup> restic.exe --repo '\\ccnas\Backup\Robust\restic\' backup 'C:\Users\Chris\Robust\Client\UofT\Case\' -v
open repository
enter password for repository:
repository d847d773 opened successfully, password is correct
lock repository
load index files
no parent snapshot found, will read all files
start scan on [C:\Users\Chris\Robust\Client\UofT\Case\]
start backup on [C:\Users\Chris\Robust\Client\UofT\Case\]
signal interrupt received, cleaning up
PS C:\Users\Chris\Robust\Backup> restic.exe --repo '\\ccnas\Backup\Robust\restic\' backup 'C:\Users\Chris\Robust\Client\UofT\*' -v
C:\Users\Chris\Robust\Client\UofT\* does not exist, skipping
Fatal: all target directories/files do not exist
PS C:\Users\Chris\Robust\Backup> restic.exe --repo '\\ccnas\Backup\Robust\restic\' backup 'C:\Users\Chris\Robust\Client\' -v
open repository
enter password for repository:
repository d847d773 opened successfully, password is correct
lock repository
load index files
no parent snapshot found, will read all files
start scan on [C:\Users\Chris\Robust\Client\]
start backup on [C:\Users\Chris\Robust\Client\]
scan finished in 1.031s: 0 files, 0 B
error: NodeFromFileInfo: Readlink: readlink \\?\C:\Users\Chris\Robust\Client\UofT: The system cannot find the file specified.
Files: 0 new, 0 changed, 0 unmodified
Dirs: 19 new, 0 changed, 0 unmodified
Data Blobs: 0 new
Tree Blobs: 6 new
Added to the repo: 5.451 KiB
processed 0 files, 0 B in 0:01
snapshot a430f65d saved
Warning: at least one source file could not be read
PS C:\Users\Chris\Robust\Backup>
What backend/server/service did you use to store the repository?
WD MyCloud PR4100
Expected behavior
Successfully back up the contents of a Dokany mounted filesystem starting at the root directory.
Actual behavior
The following message is displayed before restic terminates the backup process:
error: NodeFromFileInfo: Readlink: readlink \\?\C:\Users\Chris\Robust\Client\UofT: The system cannot find the file specified.
Steps to reproduce the behavior
On a Windows 10 operating system:
- Install Cryptomator version 1.6.4 - https://github.com/cryptomator/cryptomator
- Install Dokany version 1.5.1.1000 (x64) - https://github.com/dokan-dev/dokany
- Within Cryptomator, create a new vault.
- Configure the new vault to appear as a custom mount point using the Dokany file system and any empty folder on your C: drive.
- Using Windows Explorer, add some files and folders to the vault.
- Try to back up the contents of the vault to any archive using restic.
Do you have any idea what may have caused this?
The folder "UofT" (in the logs above) is an empty folder over which a Dokany user space filesystem is mounted by Cryptomator. All software other than restic seems to be able to access the filesystem and the files within it. restic is producing an error trying to read the root folder. I'm guessing it is having trouble with accessing the mounted file systems somehow.
Do you have an idea how to solve the issue?
restic seems to be able to access the sub folders of the mounted filesystem and everything above the mount point, only the root folder gives it trouble. Maybe there is a property or two of that mount point folder that restic needs to handle better?
The issue was discussed in the user forum here:
https://forum.restic.net/t/dokany-mounted-filesystem-inaccessible-in-windows/4582
The issue is probably related to restic issue #2708
#2708
Did restic help you today? Did it make you happy in any way?
restic is an excellent backup tool. I'm glad I found it. Thank you.