search for: close_directory

...nes 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) >...

Hello. I'm seeing several of the above messages in my smbd logs. I see three different kinds: > close_directory: Could not delete share entry for . > close_directory: Could not delete share entry for {filename} > close_remove_share_mode: Could not delete share entry for file {filename} I could find no explanation on their meaning. Anyone has a pointer? bye & Thanks av.

...4.12.10-10 using the sernet packages. After approx. 30 minutes I obtainted the following messages in syslog: root at ctdb-ho-2:~# journalctl -f -- Logs begin at Wed 2020-11-11 08:53:27 CET. -- Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.616823, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory: Could not get share mode lock for <dir> Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.693375, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory: Could not get s...

...285596, 5, pid=8606, effective(1617208032, 1617207642), real(1617208032, 0)] ../../source3/smbd/files.c:1814(file_free) file_free: freed files structure 0 (3 used) [2023/03/15 10:59:21.285611, 5, pid=8606, effective(1617208032, 1617207642), real(1617208032, 0)] ../../source3/smbd/close.c:1573(close_directory) close_directory: wrk/anly/testfolder/New folder/New folder2. Delete on close was set - deleting directory returned NT_STATUS_INVALID_PARAMETER. """""" Any help/suggestions greatly appreciated.

...gt;>../../source3/smbd/files.c:1814(file_free) >>> >>>?file_free: freed files structure 0 (3 used) >>> >>>[2023/03/15 10:59:21.285611,? 5, pid=8606, effective(1617208032, >>>1617207642), real(1617208032, 0)] >>>../../source3/smbd/close.c:1573(close_directory) >>> >>>?close_directory: wrk/anly/testfolder/New folder/New folder2. Delete on >>>close was set - deleting directory returned NT_STATUS_INVALID_PARAMETER. >>>"""""" >> >>That would normally mean the flags to unlinkat() w...

...enny 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...

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

...te SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the "Reconnecting with SMB1 for workgroup listing" path. ?? * BUG 14944: Missing pop_sec_ctx() in error path inside close_directory(). o? Pavel Filipensk? <pfilipen at redhat.com> ?? * BUG 14940: Cross device copy of the crossrename module always fails. ?? * BUG 14941: symlinkat function from VFS cap module always fails with an ???? error. ?? * BUG 14942: Fix possible fsp pointer deference. o? Volker Lendecke <vl...

...te SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the "Reconnecting with SMB1 for workgroup listing" path. ?? * BUG 14944: Missing pop_sec_ctx() in error path inside close_directory(). o? Pavel Filipensk? <pfilipen at redhat.com> ?? * BUG 14940: Cross device copy of the crossrename module always fails. ?? * BUG 14941: symlinkat function from VFS cap module always fails with an ???? error. ?? * BUG 14942: Fix possible fsp pointer deference. o? Volker Lendecke <vl...

..... D 0 Fri Dec 28 11:50:51 2012 516061624 blocks of size 1024. 489151420 blocks available smb: \blah\> During this operation, smbd throws those lines into log (timestamps removed for clarity): smbd[10578]: ../source3/smbd/close.c:1255(close_directory) smbd[10578]: Could not close dir! fname=blah/Test, fd=-1, err=9=Bad file descriptor If I do this on a share without scannedonly VFS, everything works without errors. Did I forgot about something? Regards

...n I created the W32X86/3 directory and copied all driver-files manually, I got the following message on the next installation trial: [2008/05/27 11:04:14, 2] smbd/close.c:close_normal_file(406) root closed file W32X86/3/HPBHEALR.DLL (numopen=0) NT_STATUS_OK [2008/05/27 11:04:14, 0] smbd/close.c:close_directory(430) [2008/05/27 11:04:14, 0] lib/fault.c:fault_report(41) =============================================================== [2008/05/27 11:04:14, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 8414 (3.0.29-1.1-1781-SUSE-SL10.2) Please read the Trouble-Shooting section of t...