Database corrupted (multiple common sessions found)

[burunduk]

Hi,
At every synchronisation I get error message that dtabase is corrupted (multiple common sessions found). After I ignore it the database files on both devices are updated, but at the next synchronization I get this message again. And there are problems with detection of moved files since I started to get this message. I have 3 devices to synchronise in pairs: desctop, external HDD and laptop.
This problem appeared when I moved both laptop and desctop to version 11.11.
How to solve this?

Thank you in advance

[xCSxXenon]

Check smart data of each drive with Gsmart control. That will eliminate a storage issue. FFS is running on both the desktop and laptop in two-way mode?

[Zenju]

This error shouldn't be possible™. Can you describe how exactly you handled the sync.ffs_db files (e.g. copied manually, etc.).

Which version of FreeFileSync have you been using prior?

[burunduk]

Check smart data of each drive with Gsmart control. That will eliminate a storage issue. FFS is running on both the desktop and laptop in two-way mode?

for external HDD SMART is unsupported
for both laptop and desctop HDDs SMART is supported, enabled overall health self-assessment test passed.


Normally (and when the problem occurred) FFS is running two-way mode on all devices, but before there were several times when mirror mode was used. I'm going to write more detailed account of my actions below in answer to Zenju.

[burunduk]

This error shouldn't be possible™. Can you describe how exactly you handled the sync.ffs_db files (e.g. copied manually, etc.).

Which version of FreeFileSync have you been using prior?

I didn't do anything specifically with sync.ffs_db files, but here is the full story:
This DesktopW7--extHDD--LaptopW7 synchronization system worked for me for years, it was smooth and reliable, and for that reason I don't really remember the FFS version, it was trouble-less. I have installation of 7.6 for donors, and I recall that at some point it expired, another installation file I have is for 8.1, and likely I used it after.
Last January I had problems with my desktop and eventually moved to new Windows 10, and there was many copying of files, cloning of discs etc. After that I was synchronizing the new DesktopW10--extHDD regularly without problems, likely it was FFS 8.1 version. I synchronized extHDD-LaptopW7 occasionally, and there were problems (mostly with moved folders), which I attributed to rare synchronization and didn't go into details at the time.
Since two weeks ago (mid June) I need to synchronize DesktopW10--extHDD--LaptopW7 regularly. First I synchronized DesktopW10 and extHDD without any problem, then mirrored extHDD to LaptopW7 to have kind of fresh start. However, after that problems with synchronization persisted (moved folders were suggested to be copied back). I updated LaptopW7 FFS to version 11.11, synchronized LaptopW7 and extHDD without problem (and indeed liked 11.11 more). Next, I updated DesktopW10 FSS to version 11.11 (donation edition), and after that I got for the first time this "multiple common sessions found" message, and again there was problem with moved folders. I sorted moved folders problem manually, running FFS comparison to control the process, than finally synchronized DesctopW10 and extHDD, and at each FFS run there was this "multiple common sessions found" message. After that I posted my question here and returned with extHDD to LaptopW7. It was synchronized without any error messages and other troubles (no folder was moved between the last iterations, so I cannot tell if this particular problem with the database persist or not).

Sorry for long description, I'm trying to be accurate.

[xCSxXenon]

Can you get a screenshot of that message about common sessions? I have never seen that. I wonder if a change to how FFS compares/syncs paths is causing it. That is a large update gap

[Zenju]

I suspect the data corruption mentioned in the error message was existing already in the old FFS version from before your update, and only became apparent after the more stringent checks of the new FFS version kicked in. I'm still pretty sure this error message cannot happen with the latest FFS version, but with old FFS it probably could have.

[burunduk]

Can you get a screenshot of that message about common sessions? I have never seen that. I wonder if a change to how FFS compares/syncs paths is causing it. That is a large update gap

Here it is (sorry for the delay, I was away from my Desktop).

[burunduk]

I suspect the data corruption mentioned in the error message was existing already in the old FFS version from before your update, and only became apparent after the more stringent checks of the new FFS version kicked in. I'm still pretty sure this error message cannot happen with the latest FFS version, but with old FFS it probably could have.

So, what do I do? Delete the database files and make fresh synchronization?

[xCSxXenon]

I would do that, shouldn't cause any problems

[Zenju]

Just ignoring the error and running the sync is enough. The broken db file will be overwritten. But make sure you manually check sync directions before doing this.