desktop
desktop copied to clipboard
Initial scan with virtual filesystem enabled starts from scratch if it's interrupted
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Expected behaviour
When setting up Nextcloud with virtual filesystem enabled, it tries to scan every single folder in Nextcloud. This can take a while (hours or days) since TB of data comprising hundreds of thousands of files must be scanned for changes.
Sometimes it's not possible to leave a computer on for such a longs periods, or sometimes there's a small network downtime that interrupts that scan. In those case, I'd expect that the scan continues at the point where it left.
Moreover, I noticed that the "symbolic links" (probably not the correct term) to the files stored in the server are not created until all files have been checked for changes once, so it's not possible to access any of them until the very end. It would be more convenient if they were created on the go.
Actual behaviour
The initial scan starts from scratch once again. In my case, I have to make sure that the computer that is going to use nextcloud is not turned off for ~15 hours, and make sure there will be network interruptions or nothing accesses the Nextcloud folder, since these things might trigger it to start once again from scratch.
Once workaround that I had used in the past was to exclude the largest folders first, by editing the ignored files options. But since that configuration is also saved in the nextcloud folder, and it's often still not available, it is not until the first scan has finished that you can edit that file.
Steps to reproduce
- Install Desktop client.
- Configure your account.
- Start the initial sync.
- Pause and resume the sync.
Client configuration
Client version: 3.3.5,
Operating system: both in Windows 10 and Ubuntu 20.04.
OS language: English
Installation path of client: C:\Program Files\Nextcloud
Server configuration
Nextcloud version: 22.1.0
Storage backend (external storage): sshfs
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
This is still a current issue.
I can confirm that this behavior also happens in MacOS Monterrey. I have been trying to do the initial sync in a macbook pro, and for reason, if it gets interrupted, it starts all over again. So far it's been syncing for more than 6 hours, but most of the time it's just checking the same folders over and over again.
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
@wonx let me reopen should not have been closed sorry
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
bump
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
bump
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
bump. Still a current issue.
I can confirm this issue is still present with the client v3.4.4. I reinstalled the operating system, and now the initial sync started. I estimate that it will take 10-15 uninterrupted hours to complete.
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
Bump.
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
This bug is still present.
Hi, can we reopen this bug? It's still present.
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
This bug is still present.
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
The bug is still present.
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
This is still a current issue with client 3.6.0. Please reopen.
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
Hi, can you reopen this bug again? It's still an issue.
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
Bump!
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
Hi, can you reopen this bug again? It's still an issue.