Yes, the title sounds like the problem should be obvious, but there’s more going on here.
Device A has folders X and Y. Both have the same path, but Y is a folder master.
Device B also has folders X and Y. Same config as above; same path, and Y is a master.
All shares have “ignore permissions” turned on.
Both devices share both folders with each other. (This may seem like an unusual config, but there is a purpose. The gist of it is that there are other devices not listed here that are also sharing folder Y, and device B is in a location with a faster upload pipe, but isn’t always powered on. So we want to sync quickly from B when we can.)
Expectation: The X share keeps the two folders in sync. The Y folders notice the underlying filesystem changes and come to agreement on their identical state.
Reality: The X share keeps the two folders in sync. The Y folders are hopelessly confused and neither of them agree about the folder state. Since they are both masters, this disagreement is permanent. Pressing the override button on one causes every file to be listed out of sync on the other.
Here is a /rest/db/file
request from the perspective of the out-of-sync master:
{
"availability": [
"AMSHJOQ-WMLJLRU-UZXN5PD-7XLVCQV-7D7E5CJ-UDLKX7Q-QTSWGJB-JHYGXAS"
],
"global": {
"flags": "0100666",
"localVersion": 28220,
"modified": "2012-04-28T13:35:28-04:00",
"name": "00 Alien Brambles.mp3",
"numBlocks": 32,
"size": 4097674,
"version": [
"226434223863681720:2",
"4082906498302680946:2"
]
},
"local": {
"flags": "0100666",
"localVersion": 23923,
"modified": "2012-04-28T13:35:28-04:00",
"name": "00 Alien Brambles.mp3",
"numBlocks": 32,
"size": 4097674,
"version": [
"226434223863681720:1",
"4082906498302680946:2"
]
}
}
Everything seems to be in agreement except for localVersion
and I’m not sure what significance this has.