[Bug 271096] net/netatalk3: Update to 3.1.14 results in file access failures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271096

            Bug ID: 271096
           Summary: net/netatalk3: Update to 3.1.14 results in file access
                    failures
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: marcus@FreeBSD.org
          Reporter: c.tineo@digital-light.ch
          Assignee: marcus@FreeBSD.org
             Flags: maintainer-feedback?(marcus@FreeBSD.org)

net/netatalk3: Update to 3.1.14 results in file access failures

this is similar to issue# 263624 which had been marked as fixed - but it
doesn't seem to be the case.

System:
FreeBSD 13.2-RELEASE here - netatalk3-3.1.14,1 - zfs file systems.

Example of share definition in afp.conf:

[Courant]
path = /Pool/Global/Storage/Courant
valid users = @users
file perm = 0660
directory perm = 0770

seeing thousands of entries such as those below, in /var/log/netatalk.log -
sometimes pointing at files and sometimes at directories.

As a workaround, trying to revert to 3.1.12 - can someone recommend a way to do
that on 13.2-RELEASE ?
Trying to install older version that are in /var/cache/pkg result in 'wrong
architecture' errors.


Cedric Tineo

Apr 27 10:15:40.374288 afpd[29935] {ad_open.c:818} (error:ad):
ad_header_read_ea("/Pool/Global/Storage/Courant"): invalid metadata EA this is
now being treated as a fatal error. if you see this log entry, please file a
bug ticket with your upstream vendor and attach the generated core file.
Apr 27 10:15:40.374342 afpd[29935] {ad_open.c:1280} (error:ad): ad_open_hf_ea:
unexpected: Invalid argument
Apr 27 10:15:50.366800 afpd[29935] {ad_open.c:818} (error:ad):
ad_header_read_ea("/Pool/Global/Storage/Archives/."): invalid metadata EA this
is now being treated as a fatal error. if you see this log entry, please file a
bug ticket with your upstream vendor and attach the generated core file.
Apr 27 10:15:50.367632 afpd[29935] {ad_open.c:818} (error:ad):
ad_header_read_ea("/Pool/Global/Storage/Courant"): invalid metadata EA this is
now being treated as a fatal error. if you see this log entry, please file a
bug ticket with your upstream vendor and attach the generated core file.
Apr 27 10:15:50.367686 afpd[29935] {ad_open.c:1280} (error:ad): ad_open_hf_ea:
unexpected: Invalid argument
Apr 27 10:15:50.374197 afpd[29935] {ad_open.c:818} (error:ad):
ad_header_read_ea("/Pool/Global/Storage/Archives"): invalid metadata EA this is
now being treated as a fatal error. if you see this log entry, please file a
bug ticket with your upstream vendor and attach the generated core file.
Apr 27 10:15:50.374249 afpd[29935] {ad_open.c:1280} (error:ad): ad_open_hf_ea:
unexpected: Invalid argument

-- 
You are receiving this mail because:
You are the assignee for the bug.