Emby in Proxmox LXC: Mysterious Folders Appearing on SMB Share

[rjwill10 2]

I’m running Emby (4.8.11.0) in an LXC container on Proxmox, with a TrueNAS SMB share mounted via CIFS for backups. My Emby library accesses the library folders via smb://<IP>/<share>/<folder>, and the Backup and Restore plugin is configured to use /shared/emby_backup on the same share. I couldn't get backup restore to use \\myserver. The data path is confirmed as /var/lib/emby, and the cache directory exists at /var/lib/emby/cache with correct permissions.

Emby is creating unwanted folders (dump, template, snippets, private) at the root of the SMB mount (/shared/), not in the backup directory or data path, which is /shared/emby_backup. These folders reappear after deletion

Findings:

Logs show the backup process correctly writing to /shared/emby_backup/embyserver-backup-full

(e.g., 2025-04-03 10:27:33.690 Info Backup & Restore: SyncDirectories /var/lib/emby/config to /shared/emby_backup/embyserver-backup-full/config), but no mention of the unwanted folders.

inotifywait output shows:

2025-04-03 11:26:12 /shared/ private ACCESS,ISDIR 2025-04-03 11:26:12 /shared/ private CLOSE_NOWRITE,CLOSE,ISDIR 2025-04-03 11:26:12 /shared/ snippets OPEN,ISDIR 2025-04-03 11:26:12 /shared/ snippets ACCESS,ISDIR 2025-04-03 11:26:12 /shared/template/ cache CREATE,ISDIR 2025-04-03 11:26:12 /shared/ snippets ACCESS,ISDIR 2025-04-03 11:26:12 /shared/ snippets CLOSE_NOWRITE,CLOSE,ISDIR 2025-04-03 11:26:12 /shared/template/ cache OPEN,ISDIR 2025-04-03 11:26:12 /shared/template/ cache ACCESS,ISDIR 2025-04-03 11:26:12 /shared/template/ cache

Is this expected behaviour? Should these files not be on the root disk of the Proxmox LXC? 

thanks

[Q-Droid 989]

That sounds like a Proxmox thing, not an Emby thing.

 

[rjwill10 2]

1 hour ago, Q-Droid said:

That sounds like a Proxmox thing, not an Emby thing.

 

Thanks. Yes, after further digging, it turns out that my SMB/CIFS share in Proxmox was set to accept all the available content types, which corresponded to each of the folders. Because my user permissions are broad, it seemed Emby was creating the files, but as you suggest it was Proxmox. 

Thanks