-
Notifications
You must be signed in to change notification settings - Fork 793
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
Migrate existing local Nextcloud folder to NC3.2.0 VirtualClient is not working properly #3148
Comments
Similar issue: #3082 |
I have now checked this issue with lots of installations. It seems to be related to huge folders. The error is always on a different folder. |
This comment was marked as outdated.
This comment was marked as outdated.
Problem still exists on 3.2.2 |
Had the same problem yesterday with a 21.0.1 installation and a new 3.2.2 client - in my homefolder is a photo folder with total 60.000 files in 20 subfolders (photos sorted by year) which cannot be initially syncronized. The Workaround was to select only maybe 3 or 4 subfolders to sync, do the local sync, when done add the next folders. When selecting the mainfolder with all files and subfolders the client will abort. So it could be a problem with an internal buffer overrun or whatever on the client - the amount of files seems to be too huge - no matter if I use VFS or not. I also tried to raise the variable innodb_buffer_pool_size from but it did also not fix it, so it could only be a client related problem. |
Because it seems that no one knows the problem or knows how to test it - here is a windows cmd script which you can use to create huge folders easily. Just create a folder D:\TEMP, and place a small file named bild.jpg in it. Then you specify how many folder below D:\TEMP should be created, and how many subfoldes each should have. Last you specify how many copyied of the pictures every subfolder should have. Now you can create within a few minutes a folder with 100.000 items and lots of folders which can be used for testing.
It should then be possible to upload the files to nextcloud, and use a fresh installed VM with a 3.2.2 client to see that the client will not be able to sync huge folders then. |
This comment was marked as resolved.
This comment was marked as resolved.
@wagnbeu0 this has nothing to do with the size of the sync folder but all with switching between classic sync and virtual files. I have a work in progress branch to fix that. So let's keep working on it. |
How to use GitHub
Expected behaviour
After switching from selected folder to virtual file system I get a list of all files and can decide which folder should be available locally like in OneDrive
Actual behaviour
After the Installation of the NC3.2.0 Client I turned on the feature “Support Virtual files”. It took some time, then NC told me that all is synced.
But:
1.) All my Folder s are shown the “sync” Symbol instead if the clout symbol or the green OK symbol. Even if I click on “Keep files always local”, it does not dissapear after a successful sync.
2.) Now in the NC Client I cannot select specific folders for syncronization anymore. It should therefore show all Folder in the OS with the posibilty to keep them local or only in the cloud, but my Explorer only shows me the already existing local files. Not all folders in my NC account on the server are shown locally, I therefore cannot even say “Keep them locally available” because they are not listed.
So it seems that I need to recreate the local NC folder. It this behaviour known for migrated local NC folders?
Steps to reproduce
Client configuration
Client version:
3.2.0
Operating system: Windows 10 Pro x64
OS language: German
Qt version used by client package (Linux only, see also Settings dialog):
Client package (From Nextcloud or distro) (Linux only):
Installation path of client:
C:\Program Files (x86)\Nextcloud
Server configuration
Nextcloud version: 21.0.1
Storage backend (external storage):
NFS Mount on QNAP
Client logfile:
n/a
Web server error log:
n/a
Server logfile: nextcloud log (data/nextcloud.log):
n/a
The text was updated successfully, but these errors were encountered: