search for: smbd_dirptr_get_entry

I am still fighting with this issue. I did the following: I connected to the NAS with a read-only account called kodi. I traversed various folders and I finally opened an image. Everything went fine. Looking at the logs, the get_entry mask file only shows the final folder: smbd_dirptr_get_entry mask=[Anhelina Viber] found Users/luca/Pictures/Canon/Alessandro/Amici/Anhelina Viber fname=Anhelina Viber (Anhelina Viber) smbd_dirptr_get_entry mask=[Ginevra TikTok] found Users/luca/Pictures/Canon/Alessandro/Amici/Ginevra TikTok fname=Ginevra TikTok (Ginevra TikTok) smbd_dirptr_get_entry mas...

...s >> [2017/04/21 00: 34: 52.536786, 3] ../source3/printing/pcap.c:140(pcap_cache_reload) >> >> >> >> I've been with this for many hours and I can not find the problem. I'll be very greatful. >> > > > > > I have more logs..: > > > smbd_dirptr_get_entry mask=[*] found CGS/IUBA5.CDX fname=IUBA5.CDX (IUBA5.CDX) > [2017/04/21 01:06:20.291908, 3] > ../source3/smbd/dir.c:1188(smbd_dirptr_get_entry) > smbd_dirptr_get_entry mask=[*] found CGS/Actualización de > debitos.xls fname=Actualización de debitos.xls (Actualización de > debitos.x...

...ir=Chip/FromCD/myTempHPF/ScAnVP6.2.1w/templates/Brain_Atlas [2014/02/19 15:14:13.823555, 3] ../source3/smbd/dir.c:665(dptr_create) creating new dirptr 0 for path Chip/FromCD/myTempHPF/ScAnVP6.2.1w/templates/Brain_Atlas, expect_close = 0 [2014/02/19 15:14:13.823598, 6] ../source3/smbd/dir.c:1025(smbd_dirptr_get_entry) smbd_dirptr_get_entry: dirptr 0x8092888 now at offset 0 [2014/02/19 15:14:13.823664, 3] ../source3/smbd/dir.c:1108(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found Chip/FromCD/myTempHPF/ScAnVP6.2.1w/templates/Brain_Atlas/. fname=. (.) [2014/02/19 15:14:13.823712, 6] ../source3/smb...

I'm desperate. My English is terrible, but I will try to be as clear as possible. I have Samba 4.4.4 in a Centos 7. I have many connections for each ip. The command smbstatus -b returns me infinity of these: Samba version 4.4.4 PID Username Group Machine Protocol Version Encryption Signing

...ver.c:1125(smbd_parent_loop) > Waiting for connections > [2017/04/21 00: 34: 52.536786, 3] ../source3/printing/pcap.c:140(pcap_cache_reload) > > > > I've been with this for many hours and I can not find the problem. I'll be very greatful. > I have more logs..: smbd_dirptr_get_entry mask=[*] found CGS/IUBA5.CDX fname=IUBA5.CDX (IUBA5.CDX) [2017/04/21 01:06:20.291908, 3] ../source3/smbd/dir.c:1188(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found CGS/Actualización de debitos.xls fname=Actualización de debitos.xls (Actualización de debitos.xls) [2017/04/21 01:06:20....

...ce3/printing/pcap.c:140(pcap_cache_reload) >>> >>> >>> >>> I've been with this for many hours and I can not find the problem. I'll be very greatful. >>> >> >> >> >> >> I have more logs..: >> >> >> smbd_dirptr_get_entry mask=[*] found CGS/IUBA5.CDX fname=IUBA5.CDX (IUBA5.CDX) >> [2017/04/21 01:06:20.291908, 3] >> ../source3/smbd/dir.c:1188(smbd_dirptr_get_entry) >> smbd_dirptr_get_entry mask=[*] found CGS/Actualización de >> debitos.xls fname=Actualización de debitos.xls (Actualización d...

...3] ../source3/smbd/vfs.c:1294(check_reduced_name) check_reduced_name: PENDRIVE reduced to /media/PENDRIVE [2016/05/03 11:11:07.182696, 3] ../source3/smbd/dir.c:630(dptr_create) creating new dirptr 0 for path PENDRIVE, expect_close = 0 [2016/05/03 11:11:07.183081, 3] ../source3/smbd/dir.c:1181(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found PENDRIVE/. fname=. (.) [2016/05/03 11:11:07.183460, 3] ../source3/smbd/dir.c:1181(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found PENDRIVE/.. fname=.. (..) [2016/05/03 11:11:07.183796, 3] ../source3/smbd/dir.c:1181(smbd_dirptr_get_entry) smb...

...6 16:02:01.556975, 3] ../../source3/smbd/smb2_server.c:4052(smbd_smb2_request_error_ex) smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[9] status[NT_STATUS_OBJECT_NAME_NOT_FOUND] || at ../../source3/smbd/smb2_server.c:3319 [2024/11/26 16:02:01.557205, 3] ../../source3/smbd/dir.c:734(smbd_dirptr_get_entry) smbd_dirptr_get_entry: mask=[*] found . fname=. (.) [2024/11/26 16:02:01.557230, 3] ../../source3/smbd/dir.c:734(smbd_dirptr_get_entry) smbd_dirptr_get_entry: mask=[*] found .. fname=.. (..) [2024/11/26 16:02:01.557261, 3] ../../source3/smbd/dir.c:734(smbd_dirptr_get_entry) smbd_dirptr_get...

...n Windows 7, the directory IntegrDom appears as a directory a few second and became an unknown file. Here is corresponding log (with debug level to 8): In first time we have: dos_mode: IntegrDom dos_mode_from_sbuf returning d is_in_path: IntegrDom is_in_path: match not found dos_mode returning d smbd_dirptr_get_entry mask=[*] found IntegrDom fname=IntegrDom (IntegrDom) smbd_dirptr_get_entry: dirptr 0x7f07b0f08f90 now at offset 7381146503409175813 As we can see, IntegrDom is a directory for dos_mode_from_sbuf function. When Windows 7 reload share content: dos_mode: IntegrDom dos_mode_from_sbuf returning is_in...

...ning the directory in question from client, this name is not > shown in the listing.? Samba skips this name from the listing when looping over > readdir entries: So, the same config just works in samba-4.20. There has been a quite few changes in this area in 4.20, but the order of checks in smbd_dirptr_get_entry() didn't actually change (but the code is different), -- looks like the change happened in smbd_dirptr_get_entry itself. msdfs is broken in 4.19. It worked fine in 4.18. Is no one using msdfs? I wonder why I was the first to discover this? Thanks, /mjt -- GPG Key transition (from rsa2048...

...9996, 2] ../../source3/smbd/open.c:1678(open_file) jaadmin opened file a read=No write=No (numopen=3) [2023/07/07 16:38:16.800566, 2] ../../source3/smbd/close.c:934(close_normal_file) jaadmin closed file a (numopen=1) NT_STATUS_OK [2023/07/07 16:38:16.801578, 3] ../../source3/smbd/dir.c:1057(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found . fname=. (.) [2023/07/07 16:38:16.801612, 3] ../../source3/smbd/dir.c:1057(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found .. fname=.. (..) [2023/07/07 16:38:16.801642, 3] ../../source3/smbd/dir.c:1057(smbd_dirptr_get_entry) smbd_dirptr_get...

...o such file or directory [2024/06/06 19:02:40.521781, 5, pid=1173240, effective(1000, 1000), real(1000, 0)] source3/smbd/files.c:1985(file_free) file_free: freed files structure 0 (8 used) [2024/06/06 19:02:40.521810, 3, pid=1173240, effective(1000, 1000), real(1000, 0)] source3/smbd/dir.c:750(smbd_dirptr_get_entry) smbd_dirptr_get_entry: Could not open dfstest: NT_STATUS_OBJECT_NAME_NOT_FOUND [2024/06/06 19:02:40.521845, 10, pid=1173240, effective(1000, 1000), real(1000, 0)] source3/smbd/dir.c:568(smbd_dirptr_get_entry) smbd_dirptr_get_entry: dir [.] dirptr [0x564f0a10ed10] offset [9] => dname [(fin...

Hello, Last December I wrote to the list asking about obnoxiously long freezes when using Windows 7's "explorer" to browse a samba repository. While Windows was frozen, samba's log was filling with smbd_dirptr_get_entry messages -- one for each file in a particular directory. Since I had some directories with 10,000 files, this was a slow process. Amusingly, I was not "entering" these directories with Windows. Windows was scanning "random" directories. Turns out, windows sometimes will show...

...in question from client, this name is not >>shown in the listing.? Samba skips this name from the listing when looping over >>readdir entries: > >So, the same config just works in samba-4.20. There has been a quite few changes in >this area in 4.20, but the order of checks in smbd_dirptr_get_entry() didn't actually >change (but the code is different), -- looks like the change happened in smbd_dirptr_get_entry >itself. > >msdfs is broken in 4.19. It worked fine in 4.18. > >Is no one using msdfs? I wonder why I was the first to discover this? There must not be a test f...

...ile. >> >> Here is corresponding log (with debug level to 8): >> >> In first time we have: >> >> dos_mode: IntegrDom >> dos_mode_from_sbuf returning d >> is_in_path: IntegrDom >> is_in_path: match not found >> dos_mode returning d >> smbd_dirptr_get_entry mask=[*] found IntegrDom fname=IntegrDom (IntegrDom) >> smbd_dirptr_get_entry: dirptr 0x7f07b0f08f90 now at offset >> 7381146503409175813 >> >> As we can see, IntegrDom is a directory for dos_mode_from_sbuf function. >> >> When Windows 7 reload share content: &gt...

Hello list :) I am having issues setting the "read-only" flag via Windows Explorer on my AIX Samba share and I was hoping someone out there would be able to point me into the right direction to solving this issue... I have on my AIX 7.1 system installed Samba 3.6.24 and configured, joined to our Windows domain successfully. The samba binaries I got from perzl.org/aix In my smb.conf I

...ask - 0770 browseable = yes writeable = yes Logs found in file with workstation IP: [2019/11/26 07:45:20.837967, 3] ../../source3/smbd/dir.c:662(dptr_create) creating new dirptr 0 for path ., expect_close = 0 [2019/11/26 07:45:20.838294, 3] ../../source3/smbd/dir.c:1227(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found . fname=. (.) [2019/11/26 07:45:20.838449, 3] ../../source3/smbd/dir.c:1227(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found .. fname=.. (..) [2019/11/26 07:45:20.838998, 3] ../../source3/smbd/dir.c:1227(smbd_dirptr_get_entry) smbd_dirpt...

On 07-06-2024 06:59, Michael Tokarev via samba wrote: > 07.06.2024 07:54, Jeremy Allison wrote: >>> msdfs is broken in 4.19.? It worked fine in 4.18. > > This is not entirely true. > >>> Is no one using msdfs?? I wonder why I was the first to discover this? >> >> There must not be a test for your specific use-case. >> >> MSDFS is tested in the

07.06.2024 10:13, Kees van Vloten via samba wrote: > There is a little difference with your config: I am not using symlinks in the filesystem but 'msdfs proxy' in smb.conf.? Not sure if that can be > related to your finding? msdfs proxy is not affected in this context. It is the access to msdfs-symlink *files* which broke. Thanks, /mjt -- GPG Key transition (from rsa2048 to

On Fri, Jun 07, 2024 at 11:54:28AM +0300, Michael Tokarev via samba wrote: >07.06.2024 10:13, Kees van Vloten via samba wrote: > >>There is a little difference with your config: I am not using >>symlinks in the filesystem but 'msdfs proxy' in smb.conf.? Not sure >>if that can be related to your finding? > >msdfs proxy is not affected in this context. It is