[Bug]: Nextcloud not resolving directory with name "0" and instead trying to reference subdirectory directly. #49987
Labels
2. developing
Work in progress
30-feedback
bug
feature: external storage
feature: filesystem
hotspot: filename handling
Filenames - invalid, portable, blacklisting, etc.
Bug description
I have a fileserver share mounted to my nextcloud server as an external storage at "/mnt/fileserver" mapped as an external storage to "/mnt/fileserver/surfrock66/Videos/TV". Inside here is a directory for each alphabet letter, and "0" (zero) for shows with numbers I have ripped from Blu-Ray. This works generally well, except for the folder "0". I am getting spammed multiple times a minute with the following log entry:
This folder does not exist like this; it is nested inside the "0" folder, but nextcloud appears to be skipping the 0 folder:
The other subfolders which are named with alphabet letters are fine and do not exhibit this behavior, it appears to be something specific to the "0" folder.
Steps to reproduce
Expected behavior
The folder is mounted and shows up correctly
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: