6.8.0 SMB Ver 4.11.3 significant performance decrease when opening files in folders with 1000+ files in them.

2 hours ago, je82 said:

setting case sensitive to yes in smb config does that mean in order to access a file that is on smb path you have to write out the path and filename exactly as it is with the case?

Yes.

 

This may be a problem for certain windows apps because you might create a file named "MyFile" but windows is permitted to open as "MYFILE" and this will result in "file not found".

 

In 6.8.3 we added a share SMB config setting called "Case-sensitive names" which can take on the values Auto, Yes, or Forced lower.   Here's the Help text:

 

> The default setting of **auto** allows clients that support case sensitive filenames (Linux CIFSVFS)
> to tell the Samba server on a per-packet basis that they wish to access the file system in a case-sensitive manner (to support UNIX
> case sensitive semantics). No Windows system supports case-sensitive filenames so setting this option to **auto** is the same as
> setting it to No for them; however, the case of filenames passed by a Windows client will be preserved.  This setting can result
> in reduced peformance with very large directories because Samba must do a filename search and match on passed names.
>
> A setting of **Yes** means that files are created with the case that the client passes, and only accessible using this same case.
> This will speed very large directory access, but some Windows applications may not function properly with this setting.  For
> example, if "MyFile" is created but a Windows app attempts to open "MYFILE" (which is permitted in Windows), it will not be found.
>
> A value of **Forced lower** is special: the case of all incoming client filenames, not just new filenames, will be set to lower-case.
> In other words, no matter what mixed case name is created on the Windows side, it will be stored and accessed in all lower-case.  This
> ensures all Windows apps will properly find any file regardless of case, but case will not be preserved in folder listings.
> Note this setting should only be configured for new shares.

 

"Auto" selects the current behavior (and is actually the current default).

 

If you need both faster directory operations because you have huge number of files in a directory, AND you have to preserve window case-insensitive filename semantics, then you can use "Forced lower".  But if you set this for an existing share, you will need to run a shell command to change all the file and directory names to all-lower case.

 

Then if you create "MyFile" it will be stored and show up in directory listings as "myfile".  If windows tries to open "MYFILE" samba will change requested filename on-the-fly to "myfile" and thus be able to find it.