search

samschott / maestral

Open-source Dropbox client for macOS and Linux
https://maestral.app
MIT License
3.12k stars 64 forks source link

Maestral 1.7.3 regularly does full re-uploads which result in some files becoming zero-byte #926

Open NSSynapse opened 1 year ago

NSSynapse commented 1 year ago

Apologies in advance that this bug report is less well structured than I would have liked, but the seriousness of this issue makes me very reluctant to do further testing, especially since I have a lot of files, including multiple 1Password vaults, in Dropbox folders that shared with friends and family.

Maestral used to work very well on my two Macs, but since updating to Maestral 1.7.3, I experience the following two seemingly related issues:

(1) Maestral seems to regularly do full re-uploads of all files in the Maestral folder When Maestral seemed to upload all files again after I updated it to version 1.7.3 on my first Mac, I did not think much of it and thought it was likely related to the changes to automatic re-indexing that I read about in the release notes. Since I currently only have 1.7GB in my Dropbox, those uploads also do not take very long. These (seemingly) full re-uploads, however, apparently not only happen every time I relaunch Maestral, but also regularly by themselves when Maestral is just running in the background.

(2) Some files become zero-byte (i.e., their contents are deleted) after one of those full uploads When I noticed Maestral file change notifications for some very old files, I investigated and then saw that some files had been reduced to a file size of zero. This only affected a small number of the 950 files that currently sit in my Dropbox: After the most recent relaunch of Maestral, two files lost their contents, and when I noticed the issue for the first time earlier today, something like 7 or 8 files were zero-byte. Using a Time Machine backup from last week (when I had not yet updated to Maestral 1.7.3 on either Mac), I was able to restore intact copies of those zero-length files.

Just now as I was writing this bug report, I got three more file change notifications on my MacBook Pro (of files that turned out to be zeroed-out too), and when I checked via Screen Sharing on my Mac mini at home, Maestral was indeed doing a (seemingly) full upload there again. Soon after that upload was finished on the Mac mini, Maestral started a (seemingly) full upload on my MacBook Pro.

I'll quit Maestral now on both machines to try to figure out how to proceed (i.e., whether I should downgrade Maestral or figure out some other temporary sync solution until the issue can hopefully be fixed). If there is any additional information that would be useful for me to provide, please let me know. I almost forgot: When I open Maestral's "Show Sync Issues..." window, it says "No sync issues".

System:

inklesspen commented 1 year ago

I think this may be the same issue I encountered in #925.

NSSynapse commented 1 year ago

Yes, the zero-byte part of the issue I described above seems to be extremely similar to what you have reported in https://github.com/samschott/maestral/issues/925. When I started writing this bug report, your report was not there yet and I did not check again before submitting it.

It sounds like you are not affected by the repeated uploading part of the issue, so maybe those are two separate issues that just seemed related to me, because they always happened in tandem on my machines and only older files were zeroed-out, but not the few files that I did regularly make changes to since updating Maestral to 1.9.3.

doersino commented 1 year ago

Same issue on my machine, macOS 13.4.

Maestral also seems to crash occasionally (without any relevant error or log messages), although I don't know whether that's related. It's since also been reported here: #932

I've tried rebuilding the index, but the issue reappears.

Update: Downgraded to 1.7.2., all good there.

godly-devotion commented 1 year ago

Same here, I've actually lost a file after it became zeroed out. Fortunately I was able to redownload it but I'm starting to fear losing other important documents. I've downgraded to 1.7.2 in the meantime and haven't had any issues since.

timlockridge commented 1 year ago

Echoing @inklesspen and noting that I've had several corrupted Scrivener files since upgrading to 1.7.3. I'm rolling back to 1.7.2 now.