Hello SambaTeam,

we're using vfs_media_harmony since many years and after updating our debian bullseye servers (Samba 4.13) to bookworm (Samba 4.17) vfs_media_harmony seems broken.

When we copy Avid databasefiles msmMMOB.mdb / msmFMID.pmr to a share with samba 4.19, the files disappear on the Samba view of the directory. The files still get stored in the desired format msmMMOB_IPAddress_User.mdb but do not show up when we open the directory on the windows client.

We added some debug messages and find out, mh_readdir reads the files, strips the IPAddress_User suffix and returns sucessfully. I took a look at the changes to vfs_media_harmony since 4.13 but i am not able to find any breaking stuff since then.

I'm not well aware of the vfs module concept so my question is, are there any known breaking changes in samba 4.17 ? ( vfs module structures changed a bit in 4.16, i could read )

How to reproduce:

1. Setup a Samba 4.17
2. Share config looks like:
 

[mh]
comment = Multiple Avid client access to media files
vfs objects = media_harmony
valid users = mhuser
write list = mhuser
writeable = yes
browseable = yes
veto files = /.DS_Store/._@/.Trash@/.Spotlight@/.hidden/.hotfiles@/.vol/
delete veto files = yes
veto oplock files = /*.*/
path = /srv/samba/mediaharmony
 

3. copy msmMMOB.mdb and or msmFMID.pmr file to share ( below a directory called "Avid MediaFiles/1" (the blank between Avid and MediaFiles is important)
4. Files get stored at the desired path with the expected suffix but do not show up in share when try to open

Samba 4.13 (Debian 11 Bookworm std package) works properly

regards
andy