Samba-3.0.12 and later implements a solution for sites that have experienced performance degradation due to the problem of using Samba-3 with applications that need large numbers of files (100,000 or more) per directory.
The key was fixing the directory handling to read only the current list requested instead of the old (up to samba-3.0.11) behavior of reading the entire directory into memory before doling out names. Normally this would have broken OS/2 applications, which have very strange delete semantics, but by stealing logic from Samba4 (thanks, Tridge), the current code in 3.0.12 handles this correctly.
First, you need to canonicalize all the files in the directory to have one case, upper or lower take your pick (I chose upper because all my files were already uppercase names). Then set up a new custom share for the application as follows:
Of course, use your own path and settings, but set the case options to match the case of all the files in your directory. The path should point at the large directory needed for the application any new files created in there and in any paths under it will be forced by smbd into uppercase, but smbd will no longer have to scan the directory for names: it knows that if a file does not exist in uppercase, then it doesn't exist at all.
The secret to this is really in the case sensitive = True
line. This tells smbd never to scan for case-insensitive versions of names. So if an application asks for a file
FOO, and it cannot be found by a simple stat call, then smbd will return file not
found immediately without scanning the containing directory for a version of a different case. The other
xxx case xxx lines make this work by forcing a consistent case on all files created by
Remember, all files and directories under the
path directory must be in uppercase
smb.conf stanza because smbd will not be able to find lowercase filenames with these settings. Also
note that this is done on a per-share basis, allowing this parameter to be set only for a share servicing an application with
this problematic behavior (using large numbers of entries in a directory) the rest of your smbd shares
don't need to be affected.
This makes smbd much faster when dealing with large directories. My test case has over 100,000 files, and smbd now deals with this very efficiently.