Closed valdearg closed 2 weeks ago
Hi,
Are you using Virtual File and if yes, are your json files smaller than 4KB. If yes and yes, then you might be hitting #4226 which so far has no solution AFAIK.
Cheers
Interesting, the JSON files are all below 4KB and I use the VFS, so you could definitely be onto a winner there.
Shame there's been absolutely no response on that one though as it looks like there's several bug reports with the same issue.
I suppose this is typical of the Nextcloud developers though with issues receiving no response for weeks at a time.
This should be fixed in 3.7.4. Please test and confirm
I have a similar issue going on for a few months now. I have a hosted server with multiple pc syncing, but it only does this on one of my computers. On my laptop, I have Ubuntu 23.10 with BTRFS and have no issues. But on my workstation it happens mainly with Blender files, but sometimes other files as well, although not consistent enough.
The only fix I found for these is to remove the file, wait until it syncs, then copy the files back and let it sync again. Then problem solved. I've tried regular arch package, flatpak and snap version. All have the same issue.
Config Arch with regular kernel, and BTRFS file system. Nextcloud client 3.12.3.
@valdearg As previously stated, likely fixed. Are you still experiencing this?
Apologies! Completely forgot about this one.
I'm afraid I've long since stopped using the Nextcloud Desktop client due to the stability issues.
Sounds like it was fixed about a year later so I'll go ahead and close it
Yes. I haven't experienced it lately.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
I'm having an issue where some files I've renamed using PowerShell have been synced into the NextCloud server perfectly fine, however the system keeps re-syncing these items.
The files are usually named "info.json" but other files can be in there also. The only thing in common seems to be that they are all JSON files.
The files are perfectly on the server, there are no errors in the server log when this happens.
It's not all files which are renamed in this method, it's just... some... which I understand isn't particularly helpful.
It's a bit difficult to find the exact file(s) which are being synced this way because the Desktop client interface does not actually give you the path, just the filename.
I can however see one file. When I generate the Debug file which I created after the latest sync. I think it might be something relating to the following log:
The files have been synced into the NC instance and the desktop client says that the file has been successfully renamed.
I'm slightly worried that the constant reads/writes on the DB/filesystem may not be helping performance etc.
I'm aware that we previously had this issue: https://github.com/nextcloud/desktop/issues/4016 though this is related to resetting the metadata.
Happy to provide desktop Debug archive logs privately!
Steps to reproduce
I apologise, but I'm not entirely sure how to replicate this issue reliably. This seems to affect files differently, however this is the PowerShell line that I'm using which seems to cause the most of the issues.
Move-Item -LiteralPath $filename -Destination $info_filename -Force
$filename here is a full path to a JSON file. $info_filename is then the full path just with the filename changed to info.json.
Expected behavior
Synced files should not be re-synced over and over again.
Which files are affected by this bug
info.json
Operating system
Windows
Which version of the operating system you are running.
Windows 10
Package
Other
Nextcloud Server version
24.0.2
Nextcloud Desktop Client version
3.5.1
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response