Windows accessing CIFS share with Meta Information warning/error in log

Hello,

Thanks for your report but we feel there is nothing actionable for us here.

Also you probably should not be sharing via SMB and NFS simultaneously, if you rely on alternate datastreams.

requested debug file

One additional note: This may also be Windows NFS Client doing something out of standard procedure, maybe in conjunction with DirectoryOpus. After testing it a bit today I found it has quite a few unregularities when accessing NFS shares. Sometimes the network screen shows only NFS shares, sometimes it also shows Samba shares. Setting metadata did not trigger the mount fail message but sometimes when switching folders in NFS it happened. I had asked the support of DirectoryOpus and they mentioned that the colon notation (with the additional byte after it) was standard windows notation for handling alternate data streams in NTFS and noted that I should probably report the issue here.

I am sorry but then this seems like a problem outside of FreeNAS scope.

FreeNAS simply log failed mount attempts, how clients choose to use it seems outside of our control.

On the client side there was no indication of any error but my freenas logs were full with those messages. Though I cannot surely tell if there might have been some missing meta information (Directory Opus (the file manager) seems to only use them for storing cosmetic changes like file colour). Also I am not really able to reliably reproduce it (edit: with directory opus that is). Possibly a windows nfs client could try to get Alternate Data Streams from a NFS folder accessed via \\hostnameoffreenas\path to trigger that, but that is a bit outside of my expertise.