-
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
Client just deleted 500GB + of files for no reason #703
Comments
Hi! Could you provide the client logs? Is there any reason for you to no update the server to 14? |
I'm not at my home computer now but will get logs. Is there anyway other than pressing F12 in the client to get logs because as far as I'm aware this only starts logging after you've pressed F12? As far as updating, my server only informed me of an update from 13.0.1 > 13.0.6. Now I've just clicked that update its offering 14. Is it ok to do this now without losing the logs you need? Thanks |
If there are any client logs you may find it at C:\Users[username]\AppData\Local\Nextcloud. As for the server logs, I would copy it before updating. |
There are no logs there unfortunately. All i have is a screenshot of a list of files being deleted from the client but that's not going to be any help. I don't think there's anything I can do to give you any info to why this happened is there? |
Could you try to describe what happened when the client 'decided' to delete your files? Did you update your Windows? Reboot? Renamed or moved files? Etc? |
I posted in #289 (comment) about the same issue. Linux and MacOS are also affected. |
@camilasan In my case, all I did was waiting. Nothing else. Sometimes for a long time, sometimes for a short time. It's totally random, it can happen anytime on any data and on any platform (see my link in previous comment). This should be tagged as Critical right now. |
In short: try the 2.5 version of our client (https://download.nextcloud.com/desktop/prereleases/) |
Also please provide sync logs, if the error happens again. You can find those in the following locations (for 2.5): Linux: macOS: Windows: |
Thanks for your answers. I'm still trying to reproduce this critical bug in order to get the relevant logs. Sorry but trying v2.5 of the client is not a proper solution until we are able to reproduce this bug. We need to clearly identify the source of this bug if we want to be sure that it's gone. As long as you can't tell what caused this critical erroneous behaviour (again: losing data is critical), you must assume that it's still there. Software engineering is not an experimental science, it's an exact science and it should be treated accordingly. |
I wouldn't even know what to do to reproduce it either. It's not happened since and the only big change I've made is disabling the Adobe premiere cache folder from being synced (pointless anyway). Its impossible for me to know whether this has anything to do with it. |
@Vantage-DS Do you have the option "Synchronize hidden files" enabled in the client on the computer which lost your data? And what about the other one? |
I HAVE THE SAME PROBLEM, OMG I NEED TO REDOWNLOAD 500GB over my terrible internet connection. This is horrendous, how can this be happening? Is this a Beta release, why did I upgrade? |
This reminds me of another issue I had with bitlocker recently - #3315 |
@Vantage-DS Can you test with the latest version ? In any case, to be able to work we need the desktop client logs as indicated before. |
Server - 13
Ubuntu 18 LTS
Laptop Client - 2.3.3
Windows 10 Pro
Also on network -
Mac Client 2.5 Daily
High Sierra
Expected behaviour
The 2 clients sync chosen folders with the server. Any changes are synced between the 3 computers.
Actual behaviour
With no warning, the Windows 10 client deleted over 500GB of files and folders. No reason, no pattern. It just left 3 folders behind.
The Mac client and the Server have not been affected luckily. My data is still intact on the server and mac.
The Windows 10 client thinks it's fine and has a green tick assuming its synced and up to date, but it's obviously not.
Steps to reproduce
The text was updated successfully, but these errors were encountered: