You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a fresh 18.02.0-rc13, on a fresh space, I turned on "Simple scan" import strategy. Directly on the server, I copied a folder containing 50000 file of size 1MB in the space folder.
Import started as expected, and successfully finished.
But when trying to count files with command: ls 50000files_1MB/ | wc -l
On server I obtain 50000
On dockerized oneclient (rc13) on my laptop I obtain 49847
I tried to restart update strategy in order to "rescan" the folder but without success.
In the same way, when I do the command: du -sh 50000files_1MB/
On server I obtain 49GB
On dockerized oneclient (rc13) on my laptop I obtain 0 (very long response time)
On provider admin web GUI I can see 48.8GB
However, when I do the command: ls 50000files_1MB/ | tail
On both server and oneclient I can see:
I made a similar test on 18.02.0-rc13. And all the files were scanned, inserted and oneclient does report a correct number of files. Atm. I have no way to reproduce that. Is it possible to access your environment?
On a fresh 18.02.0-rc13, on a fresh space, I turned on "Simple scan" import strategy. Directly on the server, I copied a folder containing 50000 file of size 1MB in the space folder.
Import started as expected, and successfully finished.
But when trying to count files with command:
ls 50000files_1MB/ | wc -l
On server I obtain 50000
On dockerized oneclient (rc13) on my laptop I obtain 49847
I tried to restart update strategy in order to "rescan" the folder but without success.
In the same way, when I do the command:
du -sh 50000files_1MB/
On server I obtain 49GB
On dockerized oneclient (rc13) on my laptop I obtain 0 (very long response time)
On provider admin web GUI I can see 48.8GB
However, when I do the command:
ls 50000files_1MB/ | tail
On both server and oneclient I can see:
So it seems that import process is complete
The text was updated successfully, but these errors were encountered: