Sync with virtual file error.

[wcb33]

Expected behaviour

Sync with virtual file succeed. such as the OneDrive.

Actual behaviour

sync error.

When I disable the virtual file support, the sync is succeed.

Steps to reproduce

1. Add sync folder
2. Enable virtual file support.

Client configuration

Client version: 3.2

Operating system: Win10 20H2

OS language: CN

Installation path of client: default for C:\Program files\Nextcloud.

Server configuration

Nextcloud version: docker with latest

Storage backend (external storage): linux with xfs format.

Logs

1. Client logfile:
   20210415_2031_owncloud.log.0.gz

I can find the error message:

[uberiain]

I have the same problem with this configuration:

Client configuration
Client version: 3.2

Operating system: Windows 10.0.17763.1879

OS language: ES

Installation path of client: default for C:\Program files\Nextcloud.

Server configuration:
Ubuntu 20.04

Nextcloud version: 21.0.1

Logs:

Nextcloud 3.2.0.zip

Same machine with Nextcloud desktop 3.2.0-rc3 is working without any problem.

[wagnbeu0]

I have the same problem:
I have setup a new computer to test the virtual file system because migrating my existing NC installation on my desktop was causing other problems so I wanted to test it from scratch.
On my server I have an folder “Photos” which has about 300 GB and almost 60.000 Files sorted by Year.
When I now connect the new computer to my NC server, it starts scanning all the folders. The Photos folder cannot be scanned completey, everytime it pops up with a new error message, sometimes with an “error” with a file in 2011, sometimes with an file in 2017, never the same file.

Then it starts scanning again from scratch so I am in a loop.

I use NC21.0.1 and Win10 Pre x64 with Desktop Client 3.2.0

[uberiain]

I have found that if I install the X86 version the system works fine. Can it be a problem of the msi X64?
Can someone with the same problem check this out?

[wagnbeu0]

I installed the 32bit 3.2.0 Client on two Win10 computers, but the error is still there. So for me no difference.

[mgallien]

Thanks for your report.
This issue is already fixed by #3187 .

[JustACasual]

sorry to ask, but I just downloaded and started syncing (local folder D: empty) and get this error for each virtual file it tries to create.
Should this already be fixed or is this not yet in the current release? I am on Win10 and Client Version 3.2.1

Update: hmm seems to be working if I use the default local folder on c:/user/nextcloud...
Just failing if I use my other drive D:
will investigate a bit further....

Update2: Also a sub folder of D: seems to be working. Just not D: directly

Update3: Found this comment, which explains pretty clear that using D: directly will not be possible on windows and that the only mitigation is to prohibit this in combination with Virtual Files in a future release :(
But at least I understood the issue now. will go for the sub folder then...

[FlexW]

@JustACasual Syncing a root directory like D: will never work on Windows. That is because of a limitation with the Windows API. OneDrive does also not allow it. The next release will include a warning when users try to do that.