[QA] Files with .owncloud suffix on the server cause a syncing loop

[jnweiger]

• Connect Linux client 2.6.0rc2 to owncloud server 10.3
• Wait until initial sync is done.
• Pause syncing.
• upload the same file three times to the server with the web GUI like this:
  • upload adler05.jpg and rename on the server to adler05.jpg.owncloud.owncloud
  • upload adler05.jpg and rename on the server to adler05.jpg.owncloud
  • upload adler05.jpg
• resume syncing.

The client downloads all three of them:

3& [testy:~/ownCloud5] $ ll adl*
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg.owncloud
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg.owncloud.owncloud

OK so far.

• enable virtual files ; wait for a sync -> Nothing changes.
• switch 'Availability' -> 'Free up local space'

The client starts looping.

and contents of at least one file is lost:

3& [testy:~/ownCloud5] $ ll adl*
-rw-r--r-- 1 testy testy     1 Mai 12 01:10 adler05.jpg.owncloud
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg.owncloud.owncloud
3& [testy:~/ownCloud5] $ 

[jnweiger]

related issue: #6953

[jnweiger]

when we switch back to 'Availability' -> 'Make always available locally' the looping stops, but we lost one file:

3& [testy:~/ownCloud5] $ ll adl*
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg
-rw-r--r-- 1 testy testy 99226 Mai 12 01:10 adler05.jpg.owncloud.owncloud
3& [testy:~/ownCloud5] $ 

[ogoffart]

Note: in order to reproduce the "looping", one need to "force sync"

[jnweiger]

@ogoffart Force sync is not needed here to reproduce. The client immediately starts looping after switching the availability.

[jnweiger]

when instead switching back directly from VFS with "freed local space" to non-VFS, then all three files are restored correctly.

The behaviour seems non-deterministic. Sometimes one or two files get lost on the client, but all three are on the server still. Sometimes one or two files get lost on both sides.
Running a force sync in between more often prevents the data loss for me than triggering it.

[ogoffart]

I couldn't reproduce the problem unless i do force sync. Maybe there is something that make the client not "trust" the filesystem watcher

[jnweiger]

The loop no longer happens. We see an apropriate error message, that was introduced in 48d3c84

All 3 files remain as they are. No data loss seen on the client.
Disable virtual files also preserves the files.