[Samba] Samba suddenly acting strangely

[Andrea Venturoli]

On 6/4/24 17:29, Rowland Penny via samba wrote:

> I understand your stance, you are damned if you do and damned if you
> don't.

There's one problem, which might be part of the picture above or be 
totally unrelated, but which I can reproduce easily: if I put the server 
under load, I'll start to see a lot of "file not found" on the clients.

To be more clear, if:
_ I start some heavy job on the server where Samba runs (i.e. some 
compilation, some rsync, some deep "find", etc...);
_ start some job on a client (e.g. some FreeFileSync or some compilation);
- the client will "see" all the files which are on the server, but 
report a lot of them don't exist when it tries to read them.

E.g. it will list "config.h" being present in a directory, but the 
compiler will report it as missing.



It's wholly possible that Samba is hitting some OS limit in this case 
and of course I can't expect it to work or blame it for failing, but:
_ I'd expect a more informative error (on the line of "insufficient 
resources", "unspecified error", whatever, but not "file does not 
exist", which is misleading);
_ I'd expect it to log something useful in order to grasp what the 
problem is.

However, at loglevel 1 it logs nothing; at higher levels it logs tons of 
messages and I can't easily see if some could be useful.

Is there some info on what to look for?
E.g., supposing it hits the limits of files that it can open, what would 
it log?



I think it would be useful to first solve this reproducible issue, in 
order to eventually go on with the others.

  bye & Thanks
	av.