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
ignored folders on Windows #1935
Comments
Hello @remusb , sorry for this very late answer! With the latest beta, I have a cache on a root directory (encrypted) that contains 6 folders. If I use windows explorer to navigate to one of those 6 folders that contains files and directories. I can at first see everything correctly. The folder I use for testing is quite big: it contains 190 folders which probably have subfolders as well and a lot of files. In the logs, the only issue I can see is those "Entry doesn't belong in directory "" (contains subdir) - ignoring" Also I'm not doing anything special during the 5 minutes of waiting. |
I can confirm the above issue happens to me too. All the folders and files show up perfectly on the decrypted cache mount initially. However, after a certain amount of time, the subfolders simply disappear. Remounting both the cache mount and the decrypted mount (that points to the cache mount) still show those folders as gone (when they are actually still present on Google Drive). I used both rclone 1.39 and the latest beta (rclone v1.39-015-g28480c05β) on Windows 10. |
Same here. rclone cache ran on a folder with 8 sub-folders. Each sub-folder has hundreds of files nested under them. Not using crypt. When the cache drive just mounted, everything looked fine. After a while, all the subfolders went invisible from the mounted drive, while the files are actually still on GD as could be seen from the GD web interface. I'm using Windows 10, rclone 1.39 AMD64 version of rclone. But I got 403 forbidden error from GD before/during that time. Later I mounted the drive without cache and it went on for 10 hours without missing subfolders, while I still got 403 forbidden error. Afraid that my continuing not using cache will result in 403 forbidden error again, I mounted the drive with cache again. This time I made --dir-cache-time=24h as a workaround, not sure if this could help; the subfolders haven't disappeared yet after an hour or so. Any idea if this is a valid workaround, or there's any better workaround? Update: After setting --dir-cache-time=24h, I didn't encounter the problem for a day... But after a day the folders still vanished. Now I'm setting --dir-cache-time=240h until a better workaround or fix is available :-) |
The Thanks |
I just tried the latest (February 11th) AMD64 beta. At first there were many I/O errors for my programs, possibly due to my fault of not cleaning up the old config or cache. Then I cleaned up all cache and restarted the program. It has been running smoothly for the past 12 hours. No missing files/folders until now. I encourage everyone who encountered this bug to give it a try! Thank you so much @remusb ! I'm using Windows 10. --dir-cache-time and --cache-info-age both set to 3 hours now. Running rclone mount on GD->cache->crypt. |
Awesome. So the issue can be pinned on the entry doesn't belong in directory log which was fixed by handling I'm closing the issue but if you encounter anything else, feel free to open a new one. Thank you |
I'm moving the issue in another one cause I can't seem to replicate a problem with this one on Windows and will need additional investigation. Plus, #1904 was related to another issue related to missing files caused by the old method of caching folders.
@floriansofianos I was able to replicate the same log lines in my mount but I don't see them being a problem in this case.
Here's my result:
Now, I was listing the root folder here:
/
and I can't be sure whydir1/subdir1
would be returned here and I'll take a better look at it but it is valid to be ignored cause subdir1 isn't an entry of the root. Furthermore while going in Explorer indir1
, my listing was correct and gotsubdir1
back.Are your folders still missing with the latest beta and you're just getting this log or are they actually missing if you look for them?
The text was updated successfully, but these errors were encountered: