meganz
Version 5.4 as bad as 5.3 as bad as 5.2
file names and file contents are still jumbled together in a colorful way
#917
It's halve a year now, since this problem was introduced by version 5.2 !!!
Do you know the latest version before all the bizare issues started? I might try to compile that from source, this problem is ridiculous, will have to leave mega if this doesn't stop costing me time.
Currently having issues with certain files not being able to download, it's always a new thing, never update this app once you have it working.
I'm not sure, but It hink it was 4.12. But I was told by MEGA Support::
Sie haben letztes Jahr ein Upgrade von der alten Synchronisierungs-Engine 4.12 (die diese Probleme verursacht und maskiert hat) auf die neue Engine 5.2.0 durchgeführt, und zu diesem Zeitpunkt hat die neue Engine begonnen, die bereits in Ihren synchronisierten Ordnern vorhandenen Probleme zu erkennen.
You may believe this or not. I don't.
Updated to 5.6.1-1 today Everything seemed to have gone well, the sync process did not show any errors.
However, a check showed, that a file changed today: “Documents/Data/LEMNET/New_Stations_November_2024.txt” was created as an old version of: “Documents/Data/LEMNET/Pictures_of_charging_stations/Dornbirn_Hofer-Wallenmahd_1.jpg” with the modification date: November 6, 2024. However, the file never existed before 20.11.2024 and was uploaded in the same sync process.
The content of the phantom file is that of: “Documents/Data/LEMNET/New_Stations_November_2024.txt”, which was also uploaded in the same sync process.
Another phantom file was created as the previous version of: “Documents/Radicale/var-lib-radicale-collections-collection-root-alf.zip” With the content of: “Documents/Data/TABELLEN/Fonds-NEU.ods”
Megasync version 5.6.1-1 is also a master at merging files.
Thank you very much!
Problem is solved in Version 5.9.0 The cause of the problem: Caching of inodes. Using rsync to create the directory to sync to the cloud, used new inodes for changed files. The problem could be circumvented running rsync with the option --inplace