Tons of invalid metadata EA ... #992

sfranzis · 2024-05-16T16:41:19Z

Describe the bug
I use netatalk on a XigmaNAS embedded system, which is based on FreeBSD.
Tons of "invalid metadata EA this is now being treated as a fatal error" log entries
I had this behavior with netatalk 3.1.14 and now with 3.1.18.

Due to the fact, that it's an embedded system, I cannot easily change versions of netatalk/afpd

To Reproduce
Config file afp.conf:

[Global]
hostname = discovery
uam list = uams_dhx_passwd.so uams_dhx2_passwd.so
guest account = ftp
vol dbnest = yes
vol dbpath = /opt/cnid/
disconnect time = 6
# map acls = mode
sleep time = 3
mimic model = Xserve
server quantum = 0x400000

[$u's Home]
path = /mnt/tank/home/$u/
vol charset = UTF8
valid users = @familly
file perm = 0660
directory perm = 0770
follow symlinks = yes

[Archiv]
path = /mnt/tank/archiv
vol charset = UTF8
valid users = @familly
file perm = 0660
directory perm = 0770
follow symlinks = yes

Expected behavior
no error logs

Environment

Server OS: [FreeBSD 13.3]
Filesystem: ZFS
Client OS [macOS Ventura]
Netatalk Version [3.1.18]

Logs

May 16 18:29:14 discovery 1 2024-05-16T18:29:14.820513+02:00 discovery.fritz.box afpd 56752 - - ad_open_hf_ea: unexpected: Invalid argument
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.820560+02:00 discovery.fritz.box afpd 56752 - - afp_openfork(.DS_Store): ad_open: Invalid argument
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.821254+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/home/stefan/.DS_Store"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.821321+02:00 discovery.fritz.box afpd 56752 - - ad_open_hf_ea: unexpected: Invalid argument
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.821337+02:00 discovery.fritz.box afpd 56752 - - afp_openfork(.DS_Store): ad_open: Invalid argument
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.836761+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Bilder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.837040+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Temporary Items"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.837285+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/.DS_Store"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.837565+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/web"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.837815+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Videocam"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.838058+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Network Trash Folder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.838767+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/VMs"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.839008+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/.TemporaryItems"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.839421+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Video"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.839685+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Neuer Ordner"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.839926+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Software"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.840333+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Dokumente"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.843424+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Bilder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.843697+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Temporary Items"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.843940+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/.DS_Store"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.844214+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/web"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.844428+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Videocam"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.844700+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Network Trash Folder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.845345+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/VMs"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.845588+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/.TemporaryItems"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.845994+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Video"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.846230+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Neuer Ordner"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.846466+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Software"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.846875+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Dokumente"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.849762+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Bilder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.850032+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Temporary Items"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.850275+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/.DS_Store"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.850555+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/web"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.850799+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Videocam"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.851037+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/Network Trash Folder"): 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.
May 16 18:29:14 discovery 1 2024-05-16T18:29:14.851686+02:00 discovery.fritz.box afpd 56752 - - ad_header_read_ea("/mnt/tank/archiv/VMs"): 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.

Additional context

I tried different settings I've found in other bug reports, including:
ea = ad (also sys or none)
convert appledouble = no

No change in the behavior

The text was updated successfully, but these errors were encountered:

rdmark · 2024-05-17T00:48:32Z

It would be helpful to see the actual metadata assigned to the offending files/dirs. F.e. "/mnt/tank/home/stefan/.DS_Store"

Compare the use of getfaddr in #236 (comment)

sfranzis · 2024-05-17T05:04:55Z

Hi,

handling of metadata is a bit different in FreeBSD.

discovery: log# lsextattr -fq user /mnt/tank/home/stefan/.DS_Store
DOSATTRIB	org.netatalk.Metadata
discovery: log# getextattr -fq user org.netatalk.Metadata /mnt/tank/home/stefan/.DS_Store
b	z r?DEVv?INO~?SYN?SV~?BW?BW??BW???????T
discovery: log# getextattr -fqx user org.netatalk.Metadata /mnt/tank/home/stefan/.DS_Store
00 05 16 07 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 04 00 00 00 9a 00 00 00 00 00 00 00 08 00 00 01 62 00 00 00 10 00 00 00 09 00 00 00 7a 00 00 00 20 00 00 00 0e 00 00 01 72 00 00 00 04 80 44 45 56 00 00 01 76 00 00 00 04 80 49 4e 4f 00 00 01 7e 00 00 00 04 80 53 59 4e 00 00 01 86 00 00 00 08 80 53 56 7e 00 00 01 8e 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1c 42 57 bb 1c 42 57 bb 80 00 00 00 1c 42 57 bb 00 00 00 00 ff b5 bf aa 00 00 00 00 17 00 00 00 00 00 00 00 af 18 c0 54 00 00 00 00 11 00 00 00
discovery: log# getextattr -fqs user org.netatalk.Metadata /mnt/tank/home/stefan/.DS_Store
"\000\^E\^V\000\^B\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\00\000\000\000\^D\000\000\000\M^Z\000\000\000\000\000\000\00\000\000\^Ab\000\000\000\^P\000\000\000\011\000\000\000z\000\000\000\040\000\000\000\^N\000\000\^Ar\000\000\000\^D\M^@DEV\000\000\^Av\000\000\000\^D\M^@INO\000\000\^A~\000\000\000\^D\M^@SYN\000\000\^A\M^F\000\000\00\M^@SV~\000\000\^A\M^N\000\000\000\^D\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\^\BW\M-;\^\BW\M-;\M^@\000\000\000\^\BW\M-;\000\000\000\000\M^?\M-5\M-?\M-*\000\000\000\000\^W\000\000\000\000\000\000\000\M-/\^X\M-@T\000\000\000\000\^Q\000\000\000"

The last two lines print it as hex or stringifyed.
See also: https://man.freebsd.org/cgi/man.cgi?query=getextattr

sfranzis · 2024-05-17T05:22:57Z

I found out, that there are directories, that seem to be ok. I got the metadata for one of them:

discovery: log# getextattr -fq user org.netatalk.Metadata /mnt/tank/archiv/tmp
?b	z r?DEV?INO?SYN?SV~?-K?a-٤?-K?a?z??R??2?2Ff??F
discovery: log# getextattr -fqx user org.netatalk.Metadata /mnt/tank/archiv/tmp
00 05 16 07 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 04 00 00 00 9a 00 00 00 c8 00 00 00 08 00 00 01 62 00 00 00 10 00 00 00 09 00 00 00 7a 00 00 00 20 00 00 00 0e 00 00 01 72 00 00 00 04 80 44 45 56 00 00 01 76 00 00 00 08 80 49 4e 4f 00 00 01 7e 00 00 00 08 80 53 59 4e 00 00 01 86 00 00 00 08 80 53 56 7e 00 00 01 8e 00 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2d 4b d6 61 2d d9 a4 ec 80 00 00 00 2d 4b d6 61 00 00 00 00 ad 16 7a ac de 52 8b b3 32 1d 04 00 00 00 00 00 de 32 46 66 00 00 00 00 9f 84 46 00
discovery: log# getextattr -fqs user org.netatalk.Metadata /mnt/tank/archiv/tmp
"\000\^E\^V\000\^B\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\00\000\000\000\^D\000\000\000\M^Z\000\000\000\M-H\000\000\00\000\000\^Ab\000\000\000\^P\000\000\000\011\000\000\000z\000\000\000\040\000\000\000\^N\000\000\^Ar\000\000\000\^D\M^@DEV\000\000\^Av\000\000\00\M^@INO\000\000\^A~\000\000\00\M^@SYN\000\000\^A\M^F\000\000\00\M^@SV~\000\000\^A\M^N\000\000\000\^D\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000-K\M-Va-\M-Y\M-$\M-l\M^@\000\000\000-K\M-Va\000\000\000\000\M--\^Vz\M-,\M-^R\M^K\M-32\^]\^D\000\000\000\000\000\M-^2Ff\000\000\000\000\M^_\M^DF\000"

sfranzis · 2024-05-17T13:33:26Z

Okay, probably not the most elegant solution.
I started removing ext attributes metadata from files. Then afpd will create them again.
The following command does this recursively. Use it at you own risk.

find ./ -exec rmextattr -fq user org.netatalk.Metadata {} \;

NJRoadfan · 2024-05-18T03:29:23Z

The extended attribute checking to fix the various CVE exploits is a bit too strict. The dbd tool should be able to repair these problems automatically, but the security fixes prevent the tool from fixing anything. See: #236 (comment)

rdmark · 2024-05-18T08:01:31Z

@NJRoadfan Last year we worked through several "invalid metadata EA" reports and made the checking more forgiving in certain areas. A recurring one for directories was 0 length comment I think, which we fixed in https://github.com/Netatalk/netatalk/releases/tag/netatalk-3-1-16.

I want to try to dig into these latest batch of reports to see if the offending metadata can be pinpointed, and see if the data is truly invalid and should be cleaned up, or if there are valid cases that currently fail our checks.

rdmark · 2024-05-18T10:08:02Z

Okay, probably not the most elegant solution. I started removing ext attributes metadata from files. Then afpd will create them again. The following command does this recursively. Use it at you own risk.

find ./ -exec rmextattr -fq user org.netatalk.Metadata {} \;

Ah interesting. In the main branch code (which will become 3.2.0 shortly) we changed the logic to automatically delete metadata that fails the validity check. So netatalk will effectively automate this job for you if you run that version.

My main concern is that your metadata will become "bad" again (whether a false positive or not) so I would appreciate it if you could keep an eye out for these errors to return again after some usage.

rdmark · 2024-06-02T07:56:03Z

@sfranzis A stable 3.2.0 release is now available. Do you think it would be possible to upgrade your setup to this version?

We have a new manual appendix with build instructions, including FreeBSD, which might be a good starting point for you.

When authoring the release notes, I was reminded that we actually have one more fix for EA meta data validation in this release:
#575

I have a little bit of faith that the above will resolve your issues!

sfranzis · 2024-06-04T20:30:12Z

Thanks for the new release, but in my case I use it on an embedded system. So currently I see no way to test it. We have to wait until the FreeBSD community has updated their ports and then wait for a new release of XigmaNAS.

rdmark · 2024-06-11T10:08:14Z

Well noted. I have notified the FreeBSD ports maintainer for netatalk3 about the new release, so unless he runs into some roadblocks the port should be updated shortly.

rdmark · 2024-06-25T06:30:20Z

The FreeBSD port has been updated to 3.2.0 https://www.freshports.org/net/netatalk3/

sfranzis · 2024-06-29T06:43:03Z

XigmaNAS also has updated. https://www.xigmanas.com/forums/viewtopic.php?t=2175
I updated and it looks good so far, no issues. 👍

rdmark · 2024-06-29T08:10:04Z

Thanks for letting us know!

Let me close this ticket for now. If you run into new reproducible issues, don't hesitate to throw up a new ticket.

sfranzis changed the title ~~Tons of~~ Tons of invalid metadata EA ... May 16, 2024

rdmark mentioned this issue May 18, 2024

Revert "libatalk: Restore invalid metadata cleanup in ad_open.c" #997

Closed

rdmark closed this as completed Jun 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tons of invalid metadata EA ... #992

Tons of invalid metadata EA ... #992

sfranzis commented May 16, 2024 •

edited

Loading

rdmark commented May 17, 2024

sfranzis commented May 17, 2024

sfranzis commented May 17, 2024

sfranzis commented May 17, 2024 •

edited

Loading

NJRoadfan commented May 18, 2024

rdmark commented May 18, 2024

rdmark commented May 18, 2024

rdmark commented Jun 2, 2024

sfranzis commented Jun 4, 2024

rdmark commented Jun 11, 2024

rdmark commented Jun 25, 2024

sfranzis commented Jun 29, 2024

rdmark commented Jun 29, 2024

Tons of invalid metadata EA ... #992

Tons of invalid metadata EA ... #992

Comments

sfranzis commented May 16, 2024 • edited Loading

rdmark commented May 17, 2024

sfranzis commented May 17, 2024

sfranzis commented May 17, 2024

sfranzis commented May 17, 2024 • edited Loading

NJRoadfan commented May 18, 2024

rdmark commented May 18, 2024

rdmark commented May 18, 2024

rdmark commented Jun 2, 2024

sfranzis commented Jun 4, 2024

rdmark commented Jun 11, 2024

rdmark commented Jun 25, 2024

sfranzis commented Jun 29, 2024

rdmark commented Jun 29, 2024

sfranzis commented May 16, 2024 •

edited

Loading

sfranzis commented May 17, 2024 •

edited

Loading