• [6.11.5] SMB File Share Delays with Windows - synthetic_pathref: opening failed Errors


    Geoff Bland
    • Minor

    I have started getting delays with Unraid file shares when doing any operation (viewing files in directoires, file copies etc) with Windows, this did work fine but has started happening over the last several weeks. I am also seeing associated errors in the UNRAID logs.

     

    For example, from my windows PC if I open a new directory in Windows File Explorer, then File Explorer freezes for several minutes, then I see a warning in the UNRAID logs and then immediately Windows File Explorer comes back to life and shows the directory contents.

     

    The log errors are all of the form  (when viewing a share) :

     

    May  6 12:53:55 UNRAID  smbd[31869]: [2023/05/06 12:53:55.447545,  0] ../../source3/smbd/files.c:1199(synthetic_pathref)
    May  6 12:53:55 UNRAID  smbd[31869]:   synthetic_pathref: opening [Share/[email protected]/Share/Data/C/Users/Username/AppData/Local/Google/Chrome/User Data/Default/Cache/Cache_Data/f_05a0b8 (2023_05_06 04_52_58 UTC)] failed

     

    or (when copying up an iso)

     

    May  6 12:47:28 UNRAID  smbd[31869]: [2023/05/06 12:47:28.820231,  0] ../../source3/smbd/files.c:1199(synthetic_pathref)
    May  6 12:47:28 UNRAID  smbd[31869]:   synthetic_pathref: opening [Operating Systems/Ubuntu/ubuntu-23.04-desktop-amd64 (1).iso] failed

     

    If I reboot the UNRAID server then it starts working fine for a few hours and then the freezes and log errors start up again.

     

    Restarting samba with /etc/rc.d/rc.samba restart shows the following error in the logs

     

    May  6 12:57:37 UNRAID02  smbd[31869]: [2023/05/06 12:57:37.828986,  0] ../../lib/util/fault.c:184(smb_panic_log)
    May  6 12:57:37 UNRAID02  smbd[31869]:   PANIC (pid 31869): assert failed: (fh->fd == -1) || (fh->fd == AT_FDCWD) in 4.17.3
    May  6 12:57:37 UNRAID02  smbd[31869]: [2023/05/06 12:57:37.829787,  0] ../../lib/util/fault.c:292(log_stack_trace)
    May  6 12:57:37 UNRAID02  smbd[31869]:   BACKTRACE: 39 stack frames:
    May  6 12:57:37 UNRAID02  smbd[31869]:    #0 /usr/lib64/libgenrand-samba4.so(log_stack_trace+0x2e) [0x149415d7664e]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #1 /usr/lib64/libgenrand-samba4.so(smb_panic+0x9) [0x149415d768a9]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #2 /usr/lib64/libsmbd-base-samba4.so(+0x4d10b) [0x14941615710b]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #3 /usr/lib64/libtalloc.so.2(+0x44df) [0x149415d264df]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #4 /usr/lib64/libsmbd-base-samba4.so(file_free+0xd6) [0x1494161642e6]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #5 /usr/lib64/libsmbd-base-samba4.so(close_file_free+0x29) [0x149416194d49]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #6 /usr/lib64/libsmbd-base-samba4.so(+0x5d046) [0x149416167046]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #7 /usr/lib64/libsmbd-base-samba4.so(+0x5d1ce) [0x1494161671ce]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #8 /usr/lib64/libsmbd-base-samba4.so(files_forall+0x19) [0x149416163119]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #9 /usr/lib64/libsmbd-base-samba4.so(file_close_user+0x3d) [0x14941616325d]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #10 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff+0x4d) [0x1494161e000d]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #11 /usr/lib64/libsmbd-base-samba4.so(+0xd6445) [0x1494161e0445]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #12 /usr/lib64/libdbwrap-samba4.so(+0x5d18) [0x149415a59d18]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #13 /usr/lib64/libdbwrap-samba4.so(+0x5f3a) [0x149415a59f3a]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #14 /usr/lib64/libdbwrap-samba4.so(dbwrap_traverse+0x7) [0x149415a57f67]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #15 /usr/lib64/libsmbd-base-samba4.so(smbXsrv_session_logoff_all+0x5b) [0x1494161e07fb]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #16 /usr/lib64/libsmbd-base-samba4.so(+0xdca0b) [0x1494161e6a0b]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #17 /usr/lib64/libsmbd-base-samba4.so(smbd_reinit_after_fork+0) [0x1494161e6ff0]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #18 /usr/lib64/libsmbd-shim-samba4.so(exit_server_cleanly+0x14) [0x149415d7b284]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #19 /usr/lib64/libsmbd-base-samba4.so(+0xa08e2) [0x1494161aa8e2]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #20 /usr/lib64/libtevent.so.0(tevent_common_invoke_signal_handler+0xa6) [0x149415d3d936]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #21 /usr/lib64/libtevent.so.0(tevent_common_check_signal+0xc3) [0x149415d3da93]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #22 /usr/lib64/libtevent.so.0(+0xea59) [0x149415d3fa59]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #23 /usr/lib64/libtevent.so.0(+0xcd77) [0x149415d3dd77]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #24 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x149415d38b61]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #25 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x149415d38e3b]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #26 /usr/lib64/libtevent.so.0(+0xcd17) [0x149415d3dd17]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #27 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x817) [0x1494161adce7]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #28 /usr/sbin/smbd(+0xb090) [0x5604970ba090]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #29 /usr/lib64/libtevent.so.0(tevent_common_invoke_fd_handler+0x91) [0x149415d39791]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #30 /usr/lib64/libtevent.so.0(+0xec87) [0x149415d3fc87]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #31 /usr/lib64/libtevent.so.0(+0xcd77) [0x149415d3dd77]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #32 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x91) [0x149415d38b61]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #33 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x149415d38e3b]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #34 /usr/lib64/libtevent.so.0(+0xcd17) [0x149415d3dd17]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #35 /usr/sbin/smbd(main+0x1489) [0x5604970b7259]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #36 /lib64/libc.so.6(+0x23177) [0x149415b44177]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #37 /lib64/libc.so.6(__libc_start_main+0x85) [0x149415b44235]
    May  6 12:57:37 UNRAID02  smbd[31869]:    #38 /usr/sbin/smbd(_start+0x21) [0x5604970b7b31]
    May  6 12:57:37 UNRAID02  smbd[31869]: [2023/05/06 12:57:37.830194,  0] ../../source3/lib/dumpcore.c:315(dump_core)
    May  6 12:57:37 UNRAID02  smbd[31869]:   dumping core in /var/log/samba/cores/smbd

     

    This is UNRAID version 6.11.5.

     

    I have the following SMB settings

    [global]
    idmap config * : backend = tdb
    idmap config * : range = 1000-7999
    idmap config DOMAIN : backend = rid
    idmap config DOMAIN : range = 10000-4000000000

     

    unraid02-diagnostics-20230506-1307.zip




    User Feedback

    Recommended Comments

    I was unable to find a cause for this or to fix it.

     

    In the end I had to install a new UNRAID on a different server and copy all the data across. 

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.