d0n1t3
Janeiro 18, 2023, 1:59pm
1
Windows Explorer está demorando para abrir/carregar algumas pastas e arquivos de unidade montada com o rclone browser do servidor de arquivos mega causando travamento geral do meu computador OS WINDOWS 10
como resolver ?
1 curtida
null
Janeiro 18, 2023, 4:18pm
2
Talvez possa ter ligação com o bug já reportado abaixo…
opened 05:43PM - 02 Sep 21 UTC
bug
VFS / mount
waiting for upstream...
I have mounted serveral clouds as folders via 'rclone mount'.
Regardless of the… cloud provider when I browse the folder contents or open files for viewing, sometimes the computer shows the BSOD and then reboots.
This issue happens for various clouds, I have a few Google Drive accounts, Microsoft OneDrive accounts and a Mail.ru account.
Each of these clouds/accounts mounted with rclone make the computer crash at some point.
This does not depend on the settings of the --vfs-cache-mode flag. It definitely happens on reading from the cloud, not on writing.
This is the line from my batch file, but as I said, the particular flags don't seem to matter:
start %CMD_PATH%\rclone.exe mount %REMOTE_DIR% %MOUNT_DIR% --vfs-cache-mode full --vfs-read-chunk-size-limit 0 --vfs-cache-max-size 100Gi --dir-cache-time 1m0s --poll-interval 1m0s --read-only -o FileSecurity=%SDDL% --log-file %LOG_NAME% --config %CMD_PATH%\rclone.conf %DEBUG_ARGS%
The log does not show anything I could connect to the crash. This is the example of its last lines just before the crash:
.......................
2021/09/02 19:30:01 DEBUG : pacer: low level retry 3/10 (error googleapi: Error 403: Rate Limit Exceeded, rateLimitExceeded)
2021/09/02 19:30:01 DEBUG : pacer: Rate limited, increasing sleep to 4.562147932s
2021/09/02 19:30:04 DEBUG : pacer: Reducing sleep to 0s
2021/09/02 19:30:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:30:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:31:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:31:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:32:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:32:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:33:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:33:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:34:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:34:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:35:59 DEBUG : Google drive root '': Checking for changes on remote
2021/09/02 19:35:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:36:59 INFO : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2021/09/02 19:36:59 DEBUG : Google drive root '': Checking for changes on remote
This one is for Google Drive with which I have had the most recent crash.
Logs for other clouds look obviously different, but they don't show any signs of unusual behavior just before the BSOD either.
Version info:
rclone v1.56.0
- os/version: Microsoft Windows Server 2008 R2 Standard Service Pack 1 (64 bit)
- os/kernel: 6.1.7601.24546 (x86_64)
- os/type: windows
- os/arch: amd64
- go/version: go1.16.5
- go/linking: dynamic
- go/tags: cmount
I suspect that the issue is somehow related to WinFSP, but I don't know how to investigate it.
The version of the WinFSP is 1.9.21096. I.e. the most recent stable release.
The issue usually appears either when I open a big file (e.g. video) for viewing for the first time (i.e. it is not in the cache), or when I just open the root folder of the mounted cloud after not using it long enough to make the cache get cleaned.
I never could reproduce this issue when I am actively browsing inside the mounted folder. That is, it occasionally happens only upon the first access after not using it for a while.
After the crash the empty mounted directory persists, and so I have to delete it, otherwise the mounting would not be successful.
1 curtida
Este tópico foi fechado automaticamente. Novas respostas não são mais permitidas.