fruit_pread_meta_stream: Removing [<filename>:AFP_AfpInfo] failed

  • Hi there,

    I use two Macs to connect to my SMB shares. On both machines I experience problem with grayed out/inaccessible files on shares. When I copy a file to share via Finder it immediately becomes inaccessible to execute or rename. But I still can remove it.
    I checked samba log and found this:

    For a testing purposes I installed fresh debian 10 with just samba without OMV (before I used OMV 5), so my smb.conf is:

    Files become accessible only after deleting external attribute via: setfattr -x user.DosStream.AFP_AfpInfo:\$DATA <filename>

    And for some weird reason I didn't see any "._*" files in my share directory or .recycle. But before they were always there.


    Usually I don't write forum posts about my tech problems and I solve them by myself, but this time I haven't found anything helpful in the whole Internet about this particular situation.

    Yeah, there is not so many users with Macs, but if you're are one of those, just check your samba log if there is any similar messages in there.

  • Hi Denis, hi Group,


    I have a similar problem when working with my Mac and OMV5.


    When I copy files with the Finder to the SMB-share the files are greyed out and after

    a few seconds the size will be displayed as 0.


    I think the problem started after the integration of a second harddisc for time machine.


    I will look later for the smb.conf and the error message.


    Thomas

  • Here the error messages:


    Syslog:


    Oct 27 22:02:09 PiNAS smbd[1183]: [2020/10/27 22:02:09.307044, 0] ../source3/param/loadparm.c:3343(process_usershare_file)

    Oct 27 22:02:09 PiNAS smbd[1183]: process_usershare_file: share name /cifs._smb._tcp.local./backup contains invalid characters (any of %<>*?|/\+=;:",)

    Oct 27 22:03:17 PiNAS smbd[1185]: [2020/10/27 22:03:17.422968, 0] ../source3/modules/vfs_recycle.c:424(recycle_do_touch)

    Oct 27 22:03:17 PiNAS smbd[1185]: recycle: stat for .recycle/thomas_omv/Dias/Original/scan0001.tif:AFP_AfpInfo returned No such file or directory


    Share allgemein (no time machine but the partition with problems)


    [allgemein]

    path = /srv/dev-disk-by-label-exthdd/allgemein/

    guest ok = no

    guest only = no

    read only = no

    browseable = yes

    inherit acls = yes

    inherit permissions = no

    ea support = no

    store dos attributes = no

    recycle:repository = .recycle/%U

    recycle:keeptree = yes

    recycle:versions = yes

    recycle:touch = yes

    recycle:touch_mtime = no

    recycle:directory_mode = 0777

    recycle:subdir_mode = 0700

    recycle:exclude =

    recycle:exclude_dir =

    recycle:maxsize = 0

    vfs objects = recycle catia fruit streams_xattr

    printable = no

    create mask = 0664

    force create mode = 0664

    directory mask = 0775

    force directory mode = 0775

    hide special files = yes

    follow symlinks = yes

    hide dot files = yes


    Share for Time Machine Backup


    [backup]

    path = /srv/dev-disk-by-label-tmb/backup/

    guest ok = no

    guest only = no

    read only = no

    browseable = yes

    inherit acls = yes

    inherit permissions = no

    ea support = no

    store dos attributes = no

    fruit:encoding = private

    fruit:locking = none

    fruit:metadata = netatalk

    fruit:resource = file

    fruit:time machine = yes

    vfs objects = catia fruit streams_xattr

    printable = no

    create mask = 0664

    force create mode = 0664

    directory mask = 0775

    force directory mode = 0775

    hide special files = yes

    follow symlinks = yes

    hide dot files = yes


    Section Global:


    [global]

    workgroup = WORKGROUP

    server string = %h server

    dns proxy = no

    log level = 0

    log file = /var/log/samba/log.%m

    max log size = 1000

    logging = syslog

    panic action = /usr/share/samba/panic-action %d

    encrypt passwords = true

    passdb backend = tdbsam

    obey pam restrictions = no

    unix password sync = no

    passwd program = /usr/bin/passwd %u

    passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *

    password\supdated\ssuccessfully* .

    pam password change = yes

    socket options = TCP_NODELAY IPTOS_LOWDELAY

    guest account = nobody

    load printers = no

    disable spoolss = yes

    printing = bsd

    printcap name = /dev/null

    unix extensions = yes

    wide links = no

    create mask = 0777

    directory mask = 0777

    use sendfile = yes

    aio read size = 16384

    aio write size = 16384

    time server = no

    wins support = no

    multicast dns register = no

    # Special configuration for Apple's Time Machine

    fruit:aapl = yes

    # Extra options

    min receivefile size = 16384

    write cache size = 524288

    getwd cache = yes

    socket options = TCP_NODELAY IPTOS_LOWDELAY


    Sorry for posting in this way but it was not so easy.

  • So the problem was in the order of vfs objects.

    Object recycle should be after fruit and streams_xattr.


    Bonus tip: you don't need catia object for fruit to work.


    Before: vfs objects = recycle catia fruit streams_xattr

    After: vfs objects = fruit streams_xattr recycle


    Although log messages are still in errors, in Finder files are now accessible.

  • Thanks for the hints. The order of the objects seem to be important, so i rearranged them.

    But i don't know how to handle the catia object. The documentation does not indicate any association to Apples SMB implementation, but i'm wondering why the example in the docs is configuring the fruit object.


    I finally found a howto where catia is not mentioned, so it might be an error in the fruit docs.


    The changes will be available in openmediavault 5.5.15, see https://github.com/openmediava…1b6f5ef453c2ed530fdbb862f.

  • Just as a heads-up: I don't know about the current state of extended attribute handing in SAMBA, and I'm not sure if this is still the case, but the catia object was required to allow handling of large OSX resource forks on most Unix filesystems - otherwise stream_xattr and similar workarounds stored them as normal filesystem extended attributes (i.e. typically limited to 64K).


    Most apps never created files with such large resource forks (notable exceptions being some Adobe and Apple apps - and Type 1 fonts, which were typically 0-length files with everything stored in the resource fork!), and the need for large resource fork support has probably dropped off as later OSX/MacOS versions have somewhat deprecated it as a kitchen-sink data/metadata repository, but it's probably still a good idea to leave vfs objects = catia in place unless it's causing problems with something. Most things will work without it - but some things either won't, or will give unpredictable results.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!