search

meganz / MEGAsync

Easy automated syncing between your computers and your MEGA Cloud Drive
Other
1.58k stars 276 forks source link

Megasync performs partial sync then never stops scanning #949

Open groggit opened 1 month ago

groggit commented 1 month ago

applies to LMDE5 (Debian 11 base), LMDE6 (Debian 12 base), Mega 5.2.1 64 bit, cryfs mount on local drive

I have been having a problem syncing files on my LMDE5 laptop which I've been using without issue for a couple of years. Thinking that an upgrade might solve the problem, I installed LMDE6 on my other machine and installed the desktop app.

I set up a sync on a folder containing 1,839 items totalling 1.8 GB. So initially in this scenario the Cloud drive folder contains all the files and the local folder is empty. The sync starts normally downloading all the folders and top level files and some of the sub-folder files however most are not copied, and the app remains stuck "scanning" and no more files are synced and all the subfolders remain empty or partially empty.

If I remove a previously synced top-level file on either my pc or cloud drive this is not synced.

No errors are reported by the app

Go to bed, wake up 8 hours later and the app is still "scanning". Transfer manager shows no files have been transferred.

EDIT: I duplicated the sync to a physical local folder instead of a cryfs mounted folder and all works perfectly. So it would appear to be a problem with mounted folders or cryfs?

rautamiekka commented 1 month ago

Check the logs in ~/'.local/share/data/Mega Limited/MEGAsync/logs/' for any clues.

groggit commented 1 month ago

Check the logs in ~/'.local/share/data/Mega Limited/MEGAsync/logs/' for any clues.

That folder contains 51 files named Megasync0.log through to Megasync49.log each around 600kB in size plus one file named Megasync.log at 9.1MB in size.

When I attempt to open them with a text editor my system can't figure out the character encoding so I just see a jumble of illegible characters. Thinking they might be compressed, I also tried opening them with the archive manager without success.

groggit commented 1 month ago

upon further investigation, if I mount my folder using encfs instead of cryfs everything works normally. So it appears to be an issue with the implementation of cryfs.