• [SMBD][6.11.0] Pathref errors


    sabertooth
    • Urgent

    System log is flooded with below messages (after the upgrade):

     

    Sep 26 08:47:39 UnraidZFS smbd[31175]: synthetic_pathref: opening [Someone’s MacBook Pro.sparsebundle/bands/2:AFP_AfpInfo] failed Sep 26 08:47:39 UnraidZFS smbd[31175]: [2022/09/26 08:47:39.199065, 0] ../../source3/smbd/files.c:1193(synthetic_pathref)

     

    This is applicable for all shares:

    synthetic_pathref: opening [data/backup/Downloads/ntfs.sh:AFP_AfpInfo] failed

     

    unraidzfs-diagnostics-20220926-0853.zip




    User Feedback

    Recommended Comments



    On 10/3/2022 at 2:38 PM, DjSamLb said:

    Hi I'm having the same problems without any extra settings

    My extra configuration:

     

    #unassigned_devices_start
    #Unassigned devices share includes
       include = /tmp/unassigned.devices/smb-settings.conf
    #unassigned_devices_end

     

    Update UD to remove the UD entry (it will happen automatically) and put the following in the smb-extra.conf file:

    logging = 0

     

    Link to comment

    I followed the guide here to move my settings into a separate config file and I'm still getting the error.  I don't think that is the solution.  Furthermore turning off the logging messages feels like a bandaid to me and not a real solution.

     

    Edit: I'm on 6.11.2

    Edited by gingerdude
    Link to comment

    Hello,

    I'm having the very same issue with a complete different setup: ArchLinux + smbd.

    My guess is that this issue has been introduced with the release of samba 4.17 (most probably .0 see changelog: https://www.samba.org/samba/history/samba-4.17.0.html) and should be treated upstream. Yet I can't see a bug report regarding it, so I fear we will have to wait a bit to see it fixed. There is now a bug report you can follow (or even upvote): https://bugzilla.samba.org/show_bug.cgi?id=15210

    IMHO, turning `logging` to `0` masks the issue, it doesn't fix it. It's like taking a pain killer to cure a cancer.

    Edited by dai
    Added link to bugreport
    • Like 1
    Link to comment
    On 11/7/2022 at 9:50 PM, gingerdude said:

    I followed the guide here to move my settings into a separate config file and I'm still getting the error.  I don't think that is the solution.  Furthermore turning off the logging messages feels like a bandaid to me and not a real solution.

     

    Edit: I'm on 6.11.2

     

    That's not true - it's not a bandaid.  The setting in the Unraid smb.conf file is:

    logging = syslog@0

    which sets the syslog logging level to zero.  There seems to be some issues with that setting and the logging = 0 overcomes that,  The logging = 0 is not the way to set the syslog logging level in the new samba version, but it seems to and the syslog@0 command is supposed to set the lsyslog logging level to zero which it doesn't seem to do.

     

    While I can appreciate your frustration over this issue, LT is not involved in the samba development and we just have to respond to the changes that are coming up on each new version.  It is an untennable task to check samba under every combination of hardware and software the Unraid community is using.

    Link to comment

    Understandable.  I am a software Developer.  I understand third party dependencies 🙂

     

    I'll put the config change in and watch the above issue for resolution.

    Link to comment
    On 11/3/2022 at 10:05 PM, JulienD said:

    I had the same issue on a fresh 6.11.1 and fixed it / improved copy speed by modifying in SMB settings :

    Enable SMB Multi Channel: Yes
    Enhanced macOS interoperability: No
    Samba extra configuration:
        logging = 0

     

    I don't know what individually worked...

    The enhanced macOS off setting got rid of it for me on 11.3.

    Glad to get rid of that wall of logs just from moving the steam library.

    Link to comment

    Just to add to this, 6.11 completely broke any file copies from macos OR windows to a smb share, which is fun. Cant even copy small files, I get that initial error in the log.  Going to wipe my smb settings but I flashed a stock OS and re-set everything up when going to 6.11 to try and mitigate issues like this...

    Link to comment
    On 10/10/2022 at 6:05 PM, acozad1 said:

    Hello All,

     

    I am getting this error.

     

    Stratosphere  smbd[9704]:   synthetic_pathref: opening [Movies/Significant Other 2022/Subs/4_Italian.srt] failed

     

    Every time I copy a file from my VM Windows 11 to my unraid server running 6.11.1 cache drive.

     

    Any help would be much appreciated. I have attached my logs to this post just in case anyone would like to look at them.

     

    Thank you in advance for all your help.

     

    stratosphere-syslog-20221010-2204.zip

    Exact same issue/logs as you actually...started after 6.11, 6.11.3, its still broken. I may need to roll back to the stable release as SMB is something we use all the time.  I have a basic setup, an array with a cache disk, both array and cache are encrypted. Nothing non-stock in the smb config UI.

     

    Edit: cat /etc/samba/smb-shares.conf (share that is broken, unable to write)

     

    [media]
            path = /mnt/user/media
            comment = 
            browseable = yes
            # Secure
            public = yes
            writeable = no
            write list = fs (my read/write user)
            case sensitive = auto
            preserve case = yes
            short preserve case = yes
            vfs objects = catia fruit streams_xattr
            fruit:metadata = stream
            fruit:encoding = native

     

    Edit2: I got it working sporadically by disabling MacOS Interoperability and enabling SMB Multichannel, SMB Multichannel seemed to be the one because I turn it off and all file transfers to SMB fail. With SMB MC enabled they SOMETIMES work, but its not consistent and speeds are 1mbps or so over a direct 1Gb hardwired line to a cache drive with 3000mbps write so storage and network are not bottlenecks.  File tested is a 1GB zip file so it can give the best results. This was tested from a hardwired windows PC on ethernet. Unraid is LAGG'ed to my aggregation switch using 2x10GB connections.

    Edited by Jclendineng
    Link to comment

    same issue with a win10VM writing to an unraid share

     

    I've not seen anything confirmed to identify what is causing and why..?

     

    Link to comment

    Unraid 6.11.5, copying from Windows with TotalCommander to Unraid share, no changes inany SAMBA config. 

    Share created in normal way (via GUI) and I got full log file of:

    synthetic_pathref: opening  ....... failed

     

    its a warning level only but should I care? Files are fine?

    I am copying extremely important data for me now and its a loooong process (24TB with millions of files)

     

    Log is growing:

    image.png.b6a83eb041b842c1add753f34cdbce6e.png

    Link to comment

    Also having this issue on 6.11.5 with no customisation to the samba configs, am running up to date UD plug-in as well.

     

    I do not have any macOS/Time Machine or fruit configs/setups.

     

    This purports to be affecting my Blue Iris NVR system with a standard XFS array based share (it is a hidden share). I do have a BTRFS cache drive that is involved if that helps.

    For now i will do the logging = 0 steps and see how we go.

    Link to comment

    I opened a bug report with Samba about what I thought was an issue on their side (since it wasn't introduced until 4.17.x) but they are not able to reproduce it which means it's a compile error or misconfig on the unraid side. 

     

    https://bugzilla.samba.org/show_bug.cgi?id=15247

     

    He was concerned that the server appears to be crashing with some regularity during routine operations.  Sounds familiar, doesn't it? 

    Link to comment

    SMB is still 99% broken on 6.11, I finally get files to transfer but it takes AGES and crashes half the time.  When it doesn't crash, it copies at kb/s speeds for about 30 minutes then it actually speeds up to line speed, so progress, I'm still investigating whose issue this is though, as its a deal breaker if SMB is broken.

    Link to comment

    I started getting these errors after upgrading to Windows 11, or at least that's when I noticed them.

     

    Changing the SMB settings to enable multi channel and disable enhanced macOS interoperability seems to have resolved it for me. 

     

    • Thanks 1
    Link to comment
    On 12/23/2022 at 8:21 PM, dave_m said:

    I started getting these errors after upgrading to Windows 11, or at least that's when I noticed them.

     

    Changing the SMB settings to enable multi channel and disable enhanced macOS interoperability seems to have resolved it for me. 

     

     

    Same for me.  After upgrading to V 6.11.5 and using Window 10.  Same SMB path errors in my logs.  Your solution resolved my issue as well.  Thanks!!!

    • Like 1
    Link to comment

    So I have a similar issue. Any file transfer causes tons of errors in the logs. I have a bug-report post.

     

    What should we be doing in the meantime until a fix can be completed?

    Edited by NathanR
    Link to comment

    If you like playing with fire, you can grab the latest version of Samba from Slackware:

     

    https://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/samba-4.17.5-x86_64-1.txz.mirrorlist

     

    Put that in your /boot/extra folder and it'll install Samba 4.17.5 over the version shipped by default.

     

    If you want to avoid a reboot, open a terminal and:

     

    installpkg /boot/extra/samba-4.17.5-x86_64-1.txz

     

    Then restart Samba:

     

    samba restart

     

    Link to comment
    On 2/3/2023 at 12:54 PM, NathanR said:

    Negative.

     

    Edit:

    Enable SMB Multi Channel: Yes
    
    Enhanced macOS interoperability: No

     

    Seems to work

     

    On 11/12/2022 at 8:16 PM, Mainfrezzer said:

    The enhanced macOS off setting got rid of it for me on 11.3.

    Glad to get rid of that wall of logs just from moving the steam library.

    Sorry, but I don't know if I understand it right.

     

    I have no smb-extra.conf at my /etc/samba. So I edited the /boot/config/smb-extra.conf that initially was like these:
     

    [Global]
       min protocol = SMB2
       ea support = yes
       vfs objects = catia fruit streams_xattr
       fruit:aapl = yes
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       fruit:model = MacSamba
       veto files = /._*/.DS_Store/
       delete veto files = yes
    [timemachine]
       path = /mnt/user/timemachine
       fruit:time machine = yes
       fruit:time machine max size = 2 T


    And I then add the lines and get these file:
     

    [Global]
       Enable SMB Multi Channel: Yes
       Enhanced macOS interoperability: No
       Samba extra configuration:
           logging = 0
       min protocol = SMB2
       ea support = yes
       vfs objects = catia fruit streams_xattr
       fruit:aapl = yes
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       fruit:model = MacSamba
       veto files = /._*/.DS_Store/
       delete veto files = yes
    [timemachine]
       path = /mnt/user/timemachine
       fruit:time machine = yes
       fruit:time machine max size = 2 T

     

    Then I will have to stop the array or reboot the server?

    Link to comment
    16 hours ago, Crawling5 said:

     

    Sorry, but I don't know if I understand it right.

     

    I have no smb-extra.conf at my /etc/samba. So I edited the /boot/config/smb-extra.conf that initially was like these:
     

    [Global]
       min protocol = SMB2
       ea support = yes
       vfs objects = catia fruit streams_xattr
       fruit:aapl = yes
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       fruit:model = MacSamba
       veto files = /._*/.DS_Store/
       delete veto files = yes
    [timemachine]
       path = /mnt/user/timemachine
       fruit:time machine = yes
       fruit:time machine max size = 2 T


    And I then add the lines and get these file:
     

    [Global]
       Enable SMB Multi Channel: Yes
       Enhanced macOS interoperability: No
       Samba extra configuration:
           logging = 0
       min protocol = SMB2
       ea support = yes
       vfs objects = catia fruit streams_xattr
       fruit:aapl = yes
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       fruit:model = MacSamba
       veto files = /._*/.DS_Store/
       delete veto files = yes
    [timemachine]
       path = /mnt/user/timemachine
       fruit:time machine = yes
       fruit:time machine max size = 2 T

     

    Then I will have to stop the array or reboot the server?

     

    Okey I did that and change also the interoperatibility and multi channel at GUI level.
    Now my Mac can't backup to my time machine share.

     

    Someone could help me if they have similar issue?
    It's better to not change de interoperatibility and multi channel and only leave the logging = 0?

    I also read about using a docker image for time machine but i not test it.

     

    By the way the samba logs are increasing, more slowly and I still at 1% at /var/log but I see some repeated messages at /var/log/samba/log.rpcs_lsad:

    Quote

    [2023/02/08 10:42:01,  0] ../../source3/rpc_server/rpc_worker.c:1105(rpc_worker_main)
      rpcd_lsad version 4.17.3 started.
      Copyright Andrew Tridgell and the Samba Team 1992-2022
    [2023/02/08 10:47:01,  0] ../../source3/rpc_server/rpc_worker.c:1105(rpc_worker_main)
      rpcd_lsad version 4.17.3 started.
    [2023/02/08 10:42:01,  0] ../../source3/rpc_server/rpc_worker.c:1105(rpc_worker_main)
      rpcd_lsad version 4.17.3 started.
      Copyright Andrew Tridgell and the Samba Team 1992-2022
    [2023/02/08 10:47:01,  0] ../../source3/rpc_server/rpc_worker.c:1105(rpc_worker_main)
      rpcd_lsad version 4.17.3 started.
      Copyright Andrew Tridgell and the Samba Team 1992-2022

     

    Link to comment
    On 2/7/2023 at 9:46 PM, Crawling5 said:
    [Global]
       Enable SMB Multi Channel: Yes
       Enhanced macOS interoperability: No
       Samba extra configuration:
           logging = 0
       min protocol = SMB2
       ea support = yes
       vfs objects = catia fruit streams_xattr
       fruit:aapl = yes
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       fruit:model = MacSamba
       veto files = /._*/.DS_Store/
       delete veto files = yes
    [timemachine]
       path = /mnt/user/timemachine
       fruit:time machine = yes
       fruit:time machine max size = 2 T

    Those top 3 lines you added to the conf file will break it!

     

    They are supposed to be added via the WebGUI http://{your_server_ip}/Settings/SMB

    Link to comment

    Yeah, at the end the only thing that works for me was reproduce the steps that Ed share in this video:

     

    And then when the issue of time machine looping trough "Preparing" (after I delete all the fruit extra settings on the smb-extra.config). I just type in the terminal "smbutil statshares -a" to know the samba version in use by my old Mojave MBP and it start working again. 

     

    Not extras or logging 0 needed at the moment.

    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.