New client 2.6 forgot all deselected folders, file system and client are now out of sync

[davedodo]

Expected behaviour

After updating the client to the latest version, the deselected folders should stay deselected.

Actual behaviour

Apparently, the updated client assumes that all folders are selected and starts downloading the entire cloud (except the folders that exceed the configured size limit, of course).

Even worse: I deselected a folder that was in fact previously selected before the client had the chance to redownload it, and now the files stay in the local file system, even though the client should actually delete them. Those folders now have a yellow exclamation mark icon in the Windows Explorer. What do I do about those?

Steps to reproduce

1. Update the client to the latest version with some folders deselected

Server configuration

Operating system: Ubuntu 16.04 LTS x64

Web server: Apache 2.4

Database: MySQL 5.7.27

PHP version: 7.2.24

ownCloud version: 10.2.1

Storage backend (external storage): No external storage

Client configuration

Client version: 2.6.0

Operating system: Windows 10 Pro 1903 x64

OS language: English

Installation path of client: Default

Logs

1. Client logfile .owncloudsync.log just says INST_NEW|Down for all the files previously deselected:

#=#=#=# Syncrun started 2019-11-18T13:11:02Z
#=#=#=#=# Propagation starts 2019-11-18T13:11:33Z (last step: 31367 msec, total: 31367 msec)
||Censored|INST_NEW|Down|1447277407|5643b35fbb9f4|0|00012642oceb9473c42f|4||0|0|0||
||Censored/Censored 2|INST_NEW|Down|1426619967|551069cc2051a|0|00012643oceb9473c42f|4||0|0|0||
13:11:38||Censored/Censored 2/Censored 2 02.mp3|INST_NEW|Down|1426619964|55106761a6fa3|11032912|00012646oceb9473c42f|4||200|0|0|4a2afb4f-23f9-49ac-9653-11529bffb21a|

2. Web server error log: There are no errors

[michaelstingl]

@davedodo did you switch to "Virtual Files"?

[davedodo]

@michaelstingl I don't know what "Virtual Files" is and how to switch to it, so I guess not.

One more thing I just noticed that might be of significance: those hidden database files the client creates, well, it appears to have created a fresh one prefixed .sync_, but the old one is prefixed ._sync_.

[ogoffart]

which version did you upgrade from?

[ogoffart]

It could be that for some reason, the client did not reuse the old database and created a new one, that would explain the symptoms.

[davedodo]

@ogoffart The previous one, I guess. How can I find that out? I mean, the client doesn't really ask you whether you want to update. It just does it. So it should have been 2.5.4.

[MartinMa]

According to the recent changelog are database files of new folders prefixed with .sync_ and not ._sync_ anymore.

• DB: Database path for new folders now starts with ".sync_", avoiding the "._" (macOS Journal DB filename with dot underscore #5904)

Remains to be clarified why the client (presumably) thought that it deals with a new folder, while it still seems to contain the old database file.

@davedodo Do you have any other clients where you only sync selected folders? If so, do you observe the same behavior there?

[davedodo]

@MartinMa No, only the one.

[davedodo]

What really worries me is the fact that I now have two database files in that folder. What will happen the next time I start the client? Will it use the old or the new database? Should I delete the old one?