On the client side. Renamed with Windows Explorer.
Yes, 100% data loss.
Ok, and if you did that in the web-interface, and if you did that directly on the mouted filesystem, would you have the same issue?
Perhaps the logs can help to see which level failed. Just thinking, like what would it look like if e.g. the fstab-mount was unstable? Or is there a problem with the client, is it also happening for small folder-structures (good to give instructions to reproduce), does it happen without smb-mount just on external storage on a folder on the server, âŠ
Yes, just the client ist doing it. Windows is deleting the remote folder instead of renaming it and Linux is creating 2 folders.
Dear @tflidd, this is a double thread. @wwe was asking @Sanook in another thread (100% Data loss when moving between folder - #12 by wwe) to deliver logs. But @Sanook did not deliver any logs.
Because my Nextcloud Client does not offer me to to enable logging. There is no option âEnable Loggingâ.
But at least the client shows â201 expected but 204 offeredâ. Thatâs all what i have. Sorry.
here is no need to âenableâ logging for Nextcloud desktop - it logs very verbose by default.. in Linux in ~/.config/Nextcloud/logs see
-rw-rw-r-- 1 wwe wwe 4.2M Jan 24 21:43 20260124_2143_nextcloud.log.1.gz
-rw-rw-r-- 1 wwe wwe 3.0M Jan 24 21:43 20260124_2143_nextcloud.log.2.gz
-rw-rw-r-- 1 wwe wwe 1010K Jan 24 21:43 20260124_2143_nextcloud.log.3.gz
-rw-rw-r-- 1 wwe wwe 3.5M Jan 24 21:43 20260124_2143_nextcloud.log.4.gz
-rw-rw-r-- 1 wwe wwe 4.5M Jan 24 21:43 20260124_2143_nextcloud.log.5.gz
-rw-rw-r-- 1 wwe wwe 1.7M Jan 24 21:43 20260124_2143_nextcloud.log.6.gz
-rw-rw-r-- 1 wwe wwe 287K Jan 24 21:43 20260124_2143_nextcloud.log.7.gz
-rw-rw-r-- 1 wwe wwe 496K Jan 24 21:43 20260124_2143_nextcloud.log.8.gz
-rw-rw-r-- 1 wwe wwe 14K Jan 25 07:15 20260124_2143_nextcloud.log.9
btw: Iâm merging the two threads as the issue seems the same one for files and same problem with folders.
One was to move between folders, the other was just renaming a folder. Renaming requires less interaction, no check if a file was written before it is deleted.
Before going through the verbose client logs, Iâd try to reproduce just on the web-interface and perhaps just on the mounted folder directly. If there are already issues on the lower levels, you donât need to look into the client logs.
Dear @tflidd, i do not want to discuss this in detail because it might went oftoppic, but at least one Windows Filsesystem is involved on a Wndows 11 OS. One limitation of Windows is you canât have a folder or file \test and \TEST in the same Directorry at same time. So a move files from Folder \test to Folder \TEST is on involved Windows impossible, its always by Windows limitations a renaming.
But renaming a folder from âTESTâ to âTestâ does work in Windows 11 Version 25H2 Build 26200.7623.
And the Nextcloud client is syncing it as usual.
But not within a mounted folder of a Samba server! Here, the Windows client deletes the folder insted of renaming it.
My setup:
- Synology DS220J with DSM 7.3.2 and Samba enabled
- Samba share mounted in fstab on the Nextcloud server: /mnt/SAMBA
- integrated as local external storage to Nextcloud: /SAMBA
You need to do it on the workstation, not on the server.
IIRC Synology DS220j SMB service is case insensitive.
Exactly!
Thatâs why the Nextcloud Client should also move a folder from
/SAMBA/TEST
to
/SAMBA/Test
but it deletes it instead (!)
I mean /SAMBA/TEST and not /SAMBA/Subfolder/TEST.
Nextcloud doesnât know your filesystem is case insensitive. Samba/SMB can be configured either way.
The External Storage SMB support has an option labeled Case sensitive file system for just this sort of use case.
Though since youâre mounting SMB at the OS level, thatâs not possible.
However, there is a somewhat undocumented config parameter for Local External Storage systems that you could perhaps use: localstorage.case_insensitive. It will slow things down probably. Implemented in PR #40935.
EDIT: The other option, which I meant to mention yesterday, is that it is possible to make the Synology SMB case sensitive. Use your favorite search engine to find the specifics. That may be a much better approach.
This is probably the reason why the Nextcloud Windows Client incorrectly deletes the folder on the server and the Linux Client creates two folders on the server.
It may work better with
occ conf:sys:set localstorage.caseInsensitive --type bool --value=true
but I havenât tested that because i am using both Windows and Linux on the client side. This may lead to other complications, so it is preferable not to use Samba in this manner with Nextcloud.
Thatâs what i was suggesting you to do three days before in 100% Data loss when moving between folder - #17 by adelaar