Die folgenden Elemente haben ungelöste Konflikte und werden nicht synchronisiert werden:
Ordnerpaar: \\nas1\backup\drive1 <-> \\nas2\backup\drive2.
BACKUP\folder\database.MYD: Die Dateien haben dasselbe Datum, aber unterschiedliche Größen.
Datum: Mi, 06.09.2023 09:53:58 Größe: 101.808.320 <-
Datum: Mi, 06.09.2023 09:53:58 Größe: 101.531.788 ->
Sync error due to same date but different size ?
- Posts: 21
- Joined: 18 Feb 2020
Good morning. I have some problems syncing to NAS drives. Only a few files (4 or 5) from this dir cannot be synced because of the following error in FFS.
- Posts: 4056
- Joined: 11 Jun 2019
Transfer them manually. They have different content in them but the timestamps are the same so FFS can't know which one is newer to decide which one to keep
- Posts: 21
- Joined: 18 Feb 2020
When deleting the files FFS will copy them again but the next day i get the same error ?
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
You're probably using the "old" "Update" variant. With the "changes"-based varant, this error does not occur: viewtopic.php?t=10594
- Posts: 21
- Joined: 18 Feb 2020
I had this issue never before - i think last release - btw. the "changed-based" variant is extremly slow ..
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
The "changed-based" sync config has no impact on sync performance.
- Posts: 21
- Joined: 18 Feb 2020
Hmm so maybe this happens on first run only ?
- Posts: 4056
- Joined: 11 Jun 2019
I would figure out why the content is changing every time you sync the file...
- Site Admin
- Posts: 7210
- Joined: 9 Dec 2007
Yes, this error can come up on the first run, and only there: There's no database file yet, so FFS falls back on "differences"-based sync directions for "update". In this case the actual value of the file modification time is required and "same date, different size" is therefore a conflict.Hmm so maybe this happens on first run only ? donauinsel, 26 Sep 2023, 09:26