-
Notifications
You must be signed in to change notification settings - Fork 663
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
[2.1.0] Client File Sync Problem - Wrong File Size #4505
Comments
What do you have in the server's |
Can you also try 2.1.1 please? |
there isn't any change; I installed 2.1.1 tried again with a file:c7200-advipservicesk9-mz.122-33.SRE6.image : 66MB and logs are like |
Further support see |
while syncing client shows file size wrong. a screenshot link: http://s24.postimg.org/y4pksu7c5/owncfilesizewrong.jpg i am copying a file which size is 124MB but client reads that value as 5242880KB. error gives like below. |
Expected behaviour
Sync a file. Same file size with server
Actual behaviour
Whenever sync a file with owncloud Windows Client there are some problems.
First one is while syncing file size is different with orjinal file.
For example while i sending 200MB file, client shows it as 600MB while syncing.
Second one ise after completion, when i check the file from browser. Browser shows that file as 5MB. No matter how big it is. Always file's size is 5MB
Steps to reproduce
Server configuration
Operating system: RHEL7.2
Web server: nginx 1.8
Database: Mariadb + Galera
PHP version: 7.0.3
ownCloud version: 8.2.2.2.
Storage backend: Gluster
Client configuration
Client version: 2.1.0
Operating system: Win 8.1
OS language: TR/EN
Installation path of client: default
Logs
Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.
Template for output < 10 lines
owncloud --logwindow
orowncloud --logfile log.txt
(On Windows using
cmd.exe
, you might need to firstcd
into the ownCloud directory)(See also http://doc.owncloud.org/desktop/1.8/troubleshooting.html#client-logfile )
The text was updated successfully, but these errors were encountered: