[Windows] [2.2.4 build 6408] does not re-include unavailable local sync folders when they are available again.

[TDannhauer]

Expected behaviour

After adding a folder sync to a removable drive (e.g. stick or Veracrypt container), the client complains after system boot: It marks the unaccessible folder with a read cross and says "Unable to find local sync folder."

After making the missing folder accessible, ( e.g. mounting the encrypted device), the missing folder should be re-evaluated (time or event based) by the OC client and included into sync activities as soon as it is available again.

This would make it convenient to setup local sync folders on encrypted devices.

Actual behaviour

However, after making the missing folder accessible, ( e.g. mounting the encrypted device) does not re-enable syncronisation for that folder. Only manually pausing and resuming sync triggers the OC client to re-evaluate the folder, to find it and to re-enable its synchronisation.

Steps to reproduce

Setup a folder syncronisation on a accessible removable drive (like a Truecrypt/veracrypt container)
2.
Make drive unaccessible at bootup.
3.
Setup Owncloud Client to auto start at user login
4.
Reboot system
5.
Look at Owncloud client: It marks the unaccessible folder with a read cross and says "Unable to find local sync folder."
6.
Make folder accessible again, e.g. by mounting it in Veracrypt
7.
Look at Owncloud client: It still marks the unaccessible folder with a read cross and says "Unable to find local sync folder.".
8.
Pause sync for that folder manually.
9.
Resume sync for that folder manually.
10.
Look at Owncloud client: It now finds the accessible folder and re-enables sync for that folder.

Server configuration

Operating system:
Debian Jessie

Web server:
Apache 2.4.10

Database:
Postgres 9.3

PHP version:
PHP-FPM 5.6.27

ownCloud version:
9.1.2

Storage backend (external storage):
none

Client configuration

Client version:
2.2.4 build 6408

Operating system:
Win10 64 bit

OS language:
DE

Installation path of client:
C:\Program Files (x86)\ownCloud

[SamuAlfageme]

It's not reproducing in Windows 7/10. The folder is automatically found, no need to Pause/Resume the sync. It just takes a bit (<20s) to be found and synced again.

[TDannhauer]

Have you used veracrypt with a encrypted container to reproduce? Are you usi g Win10 1607 64 bit?

I waited 120 min and it highly reproducable. Should i make a screen video?

Torben

Von unterwegs gesendet
Sent from mobile

Am 16.11.2016 um 14:39 schrieb Samuel [email protected]:

It's not reproducing in Windows 7/10. The folder is automatically found, no need to Pause/Resume the sync. It just takes a bit (<20s) to be found and synced again.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[SamuAlfageme]

@TDannhauer yup, followed every step. The thing is, I was trying to reproduce it unsuccessfully right after windows restarting and the client launch: look at this video).

But you are right, some time after the OS startup, the client is not checking if the folder is available anymore. I'm reopening to keep that availability check open. Appending this logfile here describing what's happening after adding that folder some time after the startup.

[TDannhauer]

Great, thanks for your investigation!

[ckamm]

Looking at it briefly, I see these issues:

• When the sync fails with the "Unable to find local sync folder" message, the sync isn't retried with a short interval. It probably is retried when the long-sync period expires, but that takes several hours.
• Even when a sync is triggered (though pause/unpause or force-sync/F6), the folder watchers aren't set up. And thus the folder isn't watched for local changes from then on.
• It should also work if the path goes away for an hour and then comes back (USB drive removed, then reconnected). This needs some FolderWatcher reinitialization, I guess.

[ckamm]

Work in progress branch for these issues: https://github.com/ckamm/owncloud-client/tree/late_local_folder_5317

[ckamm]

Pull request: #5381

I think there are several issues with "temporarily unavailable" sync folders (folder watchers, potentially sync journal db access) that are not yet solved. This is just the first step towards making that work.

[guruz]

@TDannhauer Would you want to try a 2.3 nightly build? http://download.owncloud.com/desktop/daily/ownCloud-2.3.0.6613-nightly20170105-setup.exe

[TDannhauer]

Great! Will do that! Is it sufficient this evening CET? Many Thanks, Torben

[guruz]

Sure :)

[TDannhauer]

The installer asks me to uninstall the older version. Does this erase my stored sync settings? Or can I simple install it over the old version without previous uninstall of the old client? My goal is to save my preferences to avoid a full re-setup of all syncing settings.

[guruz]

@TDannhauer You can install over the old version, the uninstaller won't remove settings

[TDannhauer]

Hi, works as expected, adds encrypted local folders as soon as they are made available – great! Thanks, Torben Von: Markus Goetz [mailto:[email protected]] Gesendet: Donnerstag, 5. Januar 2017 14:56 An: owncloud/client <[email protected]> Cc: Torben Dannhauer <[email protected]>; Mention <[email protected]> Betreff: Re: [owncloud/client] [Windows] [2.2.4 build 6408] does not re-include unavailable local sync folders when they are available again. (#5317) @TDannhauer <https://github.com/TDannhauer> You can install over the old version, the uninstaller won't remove settings — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5317 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AGZ6gWocwkzCv6Qsi0QRjdnTqBd04Sluks5rPPZYgaJpZM4KzlC2> . <https://github.com/notifications/beacon/AGZ6gS4PHQXOFjb3ZBhSyU5YyuNEVZ9Nks5rPPZYgaJpZM4KzlC2.gif>

[SamuAlfageme]

👍

[Challado]

Hello Friends.
These bug has appeared again. On earlier versions of owncloud all works fine, but now I need to remount unit in veracrypt and close/open owncloud to start sync volume again.