On 2020-03-31 11:38, Rowland penny via samba wrote:> I wouldn't worry about those, they are just warnings that something is > trying to delete something that it shouldn't or cannot. i.e something > that has already been deleted or it doesn't have the permission to delete.Well, I guess so :) Any hint on what that "something" is? What is a "share entry"? I guess a client is not trying to delete some *file/directory* that was already deleted? If so, I think this would be a symptom of a deeper problem.> I 'think' this has come up before, but I cannot find it, but if I am > remembering correctly, it was more of a client (MacOS ?) problem.Yes, MacOS (which is the kind of client that is giving me 99% of the problems I see lately). bye & Thanks av.
On 31/03/2020 10:57, Andrea Venturoli via samba wrote:> On 2020-03-31 11:38, Rowland penny via samba wrote: > >> I wouldn't worry about those, they are just warnings that something >> is trying to delete something that it shouldn't or cannot. i.e >> something that has already been deleted or it doesn't have the >> permission to delete. > > Well, I guess so :) > Any hint on what that "something" is? > What is a "share entry"? > I guess a client is not trying to delete some *file/directory* that > was already deleted? If so, I think this would be a symptom of a > deeper problem.A 'share entry' is exactly that, a file or directory and whilst it is probably a bit of a problem, I do not think it is a Samba problem.> > > >> I 'think' this has come up before, but I cannot find it, but if I am >> remembering correctly, it was more of a client (MacOS ?) problem. > > Yes, MacOS (which is the kind of client that is giving me 99% of the > problems I see lately).Ah, I did remember correctly, sorry but this needs to be fixed on your MacOS machines, Samba is just reporting their problem. Rowland
On 2020-03-31 12:21, Rowland penny via samba wrote: > A 'share entry' is exactly that, a file or directory You mean, it's a client trying to delete a file/directory? From what I can see, crossing smbd's log and audit log, the message > [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry for SCADENZE FORNITORI does not mean that client was trying to delete that folder. Or is it rather an internal structure in Samba referencing a file/directory? > and whilst it is > probably a bit of a problem, I do not think it is a Samba problem. Could you provide some pointer to what kind of problem this is? >> Yes, MacOS (which is the kind of client that is giving me 99% of the >> problems I see lately). > Ah, I did remember correctly, sorry but this needs to be fixed on your > MacOS machines, Samba is just reporting their problem. I possibly agree here. Only, I don't know what the problem is, so I could not fix it even if I was on the MacOS developping team (which of course I'm not). What I'm asking is not for a fix on the MacOS side; just an explanation on what Samba is complaining about. That explanation might eventually lead to actions on the client side later. bye & Thanks av.