On 2020-03-30 14:33, Rowland penny via samba wrote:> It might help if you don't crop lines like the above from your logs, out > of context they are meaningless. > > If you are going to post log fragments, post the entire log fragment and > a few lines above and below it.Sorry. Here a full excerpt:> [2020/03/30 14:56:31.559263, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry for . > [2020/03/30 14:56:31.576680, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry for . > [2020/03/30 15:00:51.389289, 0] ../../source3/smbd/close.c:1126(close_directory) > close_directory: Could not get share mode lock for . > [2020/03/30 15:04:26.306712, 0] ../../source3/smbd/close.c:1126(close_directory) > close_directory: Could not get share mode lock for SCADENZE FORNITORI > [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry for SCADENZE FORNITORIbye & Thanks av.
On 30/03/2020 14:29, Andrea Venturoli wrote:> Here a full excerpt: > >> [2020/03/30 14:56:31.559263,? 0] >> ../../source3/smbd/close.c:1214(close_directory) >> ? close_directory: Could not delete share entry for . >> [2020/03/30 14:56:31.576680,? 0] >> ../../source3/smbd/close.c:1214(close_directory) >> ? close_directory: Could not delete share entry for . >> [2020/03/30 15:00:51.389289,? 0] >> ../../source3/smbd/close.c:1126(close_directory) >> ? close_directory: Could not get share mode lock for . >> [2020/03/30 15:04:26.306712,? 0] >> ../../source3/smbd/close.c:1126(close_directory) >> ? close_directory: Could not get share mode lock for SCADENZE FORNITORI >> [2020/03/30 15:23:16.754076,? 0] >> ../../source3/smbd/close.c:1214(close_directory) >> ? close_directory: Could not delete share entry for SCADENZE FORNITORII 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. 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. Rowland
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.