• [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



    Same issue here:

     

    SMB

     

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

    #macOS config start
    [Global]
       vfs objects = catia fruit streams_xattr
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       spotlight backend = tracker

    Link to comment

    For those with macOS issues - please do not put anything related to "fruit" settings in config/smb-extra.conf. 

    That file will set "global settings" and the fruit stuff needs to be per-share.  Only create/modify config/smb-fruit.conf if you want to experiment with non-default settings.

     

    Also, please set your 'flash' export setting to No if running 6.11.0 or earlier.  Once 6.11.1 is published you should be able to re-export 'flash' share if you want (though not recommended).

    Link to comment

    Same Issue here on 6.11.1 when using Robocopy to mirror a number of files from a windows machine to the share, no macOS devices on the network.

     

    smb-extra.conf:

    #async io
    aio read size = 1
    aio write size = 1
    
    #turn off sendfile due to problems with ZFS
    use sendfile = no
    
    #Enable RSS
    server multi channel support = yes
    interfaces = "[IP of the Server];capability=RSS,speed=10000000000"
    
    [share]
        path = /mnt/zpool/share
        comment = share
        browseable = yes
        guest ok = no
        writeable = no
        read list = @users
        write list = @users
        valid users =  @users
        case sensitive = auto
        preserve case = yes
        short preserve case = yes
        vfs objects = catia fruit streams_xattr shadow_copy2
        shadow: snapdir = .zfs/snapshot
        shadow: format = zfs-auto-snap_%S-%Y-%m-%d-%H%M   
        shadow: sort = desc
        shadow: localtime = no
        veto files = /._*/.DS_Store/
    	
    [more shares with the same settings]

    Removing fruit and the veto files from the share and restarting samba did not change the behavior.

    smb-shares.conf is empty.

     

    The Robocopy command for reference:

    robocopy.exe /SD:C:\Directory /DD:\\NAS\share\folder /IF *.* /XD [some excluded subfolders] /S /E /DCOPY:DA /COPY:DAT /PURGE /MIR /xjd /R:1 /W:0 /NFL /NDL /NP /NS /NC /MT:32

     

    Link to comment

    Having the same issue; macOS time machine backups involved, had the samba fruit settings before, like a lot of you guys as well.

    Converted (as good as I could) to smb fruit config on flash drive, made sure that nothing is left in smb-share.conf / global SMB settings in UNRAID gui. Restarted everything.

     

    Log is still being flodded, but at least time machine is still working.

    Link to comment

    Upgraded to 6.11.1, now I can't see any ZFS dataset. Great.

     

    EDIT-1: Went back to 6.11.0.

    EDIT-2: Upgrade again to 6.11.1. ZFS is fine, not sure what happened.

    Edited by sabertooth
    • Like 1
    Link to comment

    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

    • Like 1
    Link to comment

    Hey there.

     

    I'm having the same issue and the logs are full now. 

     

    Anyone fount a solution to that ? 

     

    I did upgrade from 6.10.3 to 6.11.1 and the error started and I cannot backup using timemachine anymore.

    Link to comment

    Same issue for me too.

    It is my Windows 11 VM copying files from my Blue Iris NVR software to my unraid share.

    I do have a time machine share set up for a Mac too but doesn't look to be related?


    image.png.2cd242d9e6c5366b75bd623dceb19afc.png

    Link to comment

    I made Time machine work again after @dlandon recommendation to copy the smb-extra.conf file to /boot/config

     

    I have set the following content. 

     

    # global parameters are defined in /etc/samba/smb.conf
    # current per-share Unraid OS defaults
    vfs objects = catia fruit streams_xattr
    #fruit:resource = file
    fruit:metadata = stream
    #fruit:locking = none
    #fruit:encoding = private
    fruit:encoding = native
    #fruit:veto_appledouble = yes
    #fruit:posix_rename = yes
    #readdir_attr:aapl_rsize = yes
    #readdir_attr:aapl_finder_info = yes
    #readdir_attr:aapl_max_access = yes
    #fruit:wipe_intentionally_left_blank_rfork = no
    #fruit:delete_empty_adfiles = no
    #fruit:zero_file_id = no
    # these are added automatically if TimeMachine enabled for a share:
    #fruit:time machine
    #fruit:time machine max size = SIZE

     

    But, restarting samba did not fix the transfer problem. Rebooting the server fixed the Time Machine sync issue.

     

    I still have a flood of logs for the error

     

    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.264730,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/759:AFP_AfpInfo] failed
    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.272952,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/759:AFP_AfpInfo] failed
    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.302927,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/1a1c:AFP_AfpInfo] failed
    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.324951,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/28a:AFP_AfpInfo] failed
    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.343093,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/6fa:AFP_AfpInfo] failed
    Oct 13 19:03:02 Andromeda  smbd[21319]: [2022/10/13 19:03:02.350699,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 13 19:03:02 Andromeda  smbd[21319]:   synthetic_pathref: opening [Vincent’s MacBook Pro.sparsebundle/bands/6fa:AFP_AfpInfo] failed

    andromeda-diagnostics-20221013-1857.zip

     

    Link to comment

    Hello,

     

    I'd like to report the same synthetic_pathref issues. These are logged upon any SMB file access - even listing a directory - although there are no issues with the actual access from a client.

     

    For example, Time Machine backups are working OK, just that the syslog is filled with entries such as these until I run out of log space:

     

    Oct 11 06:23:30 NAS  smbd[3868]: [2022/10/11 06:23:30.418333,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 11 06:23:30 NAS  smbd[3868]:   synthetic_pathref: opening [RH MacBook Pro 13.sparsebundle/bands/1961:AFP_AfpInfo] failed
    Oct 11 06:23:30 NAS  smbd[3868]: [2022/10/11 06:23:30.421560,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 11 06:23:30 NAS  smbd[3868]:   synthetic_pathref: opening [RH MacBook Pro 13.sparsebundle/bands/18a1:AFP_AfpInfo] failed
    Oct 11 06:23:30 NAS  smbd[30538]: [2022/10/11 06:23:30.422283,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)

     

    I'd be happy to share a full diagnostics output with Limetech if it will help, I'd prefer not to post my syslog here as with these errors, full pathnames including names of family members are exposed.

     

    Edited to add that these entries are logged upon access from both Windows 11 and MacOS 12.6 clients. It's not just MacOS-specific.

     

    Thanks.

    Edited by Oldbean57
    Added clarity around client types.
    Link to comment

    @guyonphone Let me know if this works for you. I am interested in attempting the same thing. Maybe I missed something up while upgrading.

     

    Please let me know what version you downgrade to.  

    Link to comment

    @acozad1 I downgraded from 6.11.1 to 6.11.0 and then re-updated back to 6.11.1. Unfortunately this did not fix my issue and I am still having the issue. I am noticing that I am having odd issues where I am unable to rename some directories via windows SMB.

    Edited by guyonphone
    • Thanks 1
    Link to comment

    For anyone having this issue, try adding the following to the smb-extra.conf file:

    log level = 0

     

    If that doesn't work, try adding this:

    logging = 0

     

    I'm working with the recycle bin plugin and the latest version of Samba seems to have a lot of changes to logging.  I'm thinking the log message you are seeing is a debug message and shouldn't be showing up in the syslog.

    • Thanks 1
    Link to comment

    Thank-you for the suggestion @dlandon

     

    I've tested here and setting "logging = 0" in smb-extra.conf worked to disable the logging (I used the SMB Extras GUI in SMB Settings).

     

    "log level = 0" did not work, as you suspected.

     

    This is a good workaround while the Samba logging changes are understood.

     

    Thanks very much.

    Link to comment

    Same issues here with 6.11.1

    My logs are flooded with this error:
     

    Oct 17 12:15:15 OrigamiNET  smbd[17095]: [2022/10/17 12:15:15.334182,  0] ../../source3/smbd/files.c:1193(synthetic_pathref)
    Oct 17 12:15:15 OrigamiNET  smbd[17095]:   synthetic_pathref: opening [filepath/file:AFP_AfpInfo] failed

     

    Here is my Samba extra configuration:
     

    [global]
       vfs objects = catia fruit streams_xattr
       fruit:nfs_aces = no
       fruit:zero_file_id = yes
       fruit:metadata = stream
       fruit:encoding = native
       spotlight backend = tracker

    [system]
       path = /mnt/user/system
       veto files = /._*/.DS_Store/
       delete veto files = yes
       spotlight = yes

    Would appreciate any guidance here as it's dragging my server operations down.

    Also - my foolish mistake here, but does anyone have a copy of the default unRAID Samba extra configuration so I can revert back to defaults for testing purposes?

    Thank you.

    Link to comment
    3 hours ago, DaveHavok said:

    Would appreciate any guidance here as it's dragging my server operations down.

    Read the post just above yours.

     

    3 hours ago, DaveHavok said:

    Also - my foolish mistake here, but does anyone have a copy of the default unRAID Samba extra configuration so I can revert back to defaults for testing purposes?

    It's empty.

     

    Don't put fruit settings in smb-extra.conf.  Earlier posts describe how to move the /etc/samba/smb-fruit.conf file to the flash and make changes there.

    Link to comment

    Thanks @dlandon!

    I reverted my SMB extras configuration back to this with all the fruit settings removed and it eliminated the synthetic_pathref errors that were generating previously:
     

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

    [global]
       spotlight backend = tracker

    [system]
       path = /mnt/user/system
       veto files = /._*/.DS_Store/
       delete veto files = yes
       spotlight = yes


    I'll take a look the /etc/samba/smb-fruit.conf steps you mentioned from a previous post. 

    Cheers.

    Link to comment

    Also have this same issue when copying from a windows drive to the unraid server. Doesn't seem to effect the actual files themselves from working properly but the huge amount of the errors is crazy. This is a brand new install of the latest version.

     

    Hopefully unraid will fix his. Or if something I can do to resolve it now, let me know. I have attached my diagnostics report.

    tower-diagnostics-20221021-1218.zip

    Edited by CyberKNight
    • Like 1
    Link to comment

    Update the UD plugin to remove the "#unassigned_devices" entry in the smb-extra.conf file.  Also update the Recycle Bin plugin to remove that entry from smb-extra.conf.

     

    As explained above, don't do any fruit settings in the smb-extra.conf file.  Use the smb-fruit.conf file.

     

    Several users have reported the following in the smb-extra.conf file will stop these mesages:

    logging = 0

     

    Link to comment

    I have the same problem whenever I try to scan any files from my Brother document scanner model ADS-2600We.

     

    That has never been a problem before but now I am getting error messages and the scanner just says Sending Error when ever I try to scan anything. 

    Link to comment

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

    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.