-
Notifications
You must be signed in to change notification settings - Fork 806
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
[Bug]: Nextcloud virtual files cannot sync some files #7663
Comments
There is a bug report for this: #7657 |
@camilasan The biggest problem right now is that Nextcloud crashes when certain files are converted from virtual files to real files. There is nothing special about the files that cause the crashes.The only thing that is certain is that when the number of files is large, the probability of crash is close to 100% |
The synchronization is terminated at a temporary file of a file in the synchronization process, with the name pattern of |
Finally, I would like to add that due to the unexpected crash of Nextcloud, temporary files were not processed. If they are not cleaned up manually, the temporary files will be synchronized to the Server when Nextcloud is started again. Maybe they need to be ignored by default. |
Bug description
I hate to say it, but Nextcloud 3.15 is the worst release ever.
This configuration is known to lead to data loss and is no longer upported. Please consider removing this folder from the account and adding it again.
Currently, Nextcloud is unavailable.
Steps to reproduce
Expected behavior
。。。
Which files are affected by this bug
all
Operating system
Windows
Which version of the operating system you are running.
Windows10、Windows11
Package
Official Windows MSI
Nextcloud Server version
30.04
Nextcloud Desktop Client version
3.15.0
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
log.zip
The text was updated successfully, but these errors were encountered: