New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"malformed AppleDouble" and "Input/output error" messages on 3.1.14 #270
Comments
These volumes are old, and yes, they were probably created using netatalk2. I remember using the version 2 long time ago. But I don't remember doing a conversion of these volumes. Perhaps they were converted automagically by netatalk3? |
@rdmark, thanks for your assistance. I've ran the command
Do you think it will be safe to run |
Are you able to take a backup of the volume before running |
@rdmark, OK thanks. |
@mikaku I would definitely stop netatalk first to avoid any potential race condition when both processes try to operate on the database at the same time. |
It seems that
So I did it with Netatalk running and
Now I'll wait for Monday to see if users don't have any problem (:crossed_fingers:). |
I still see messages like this:
Anyway, since they are really low I can live with them. |
Reopening this since the original issue was reported by another user in #368 The root cause, I think, is that netatalk is trying to read AD headers from a symlink, which it shouldn't. |
I have yet to be able to reproduce this, after playing around with symlinks... |
I just saw that my current version was I'll confirm you in the next days if I still see those messages in the log. |
Today appeared the following message repeated a lot of times, always with the same file name:
I'll continue checking if the message appears with different file names. |
Curious, so the faulty metadata seems to originate with an Adobe Illustrator file.
What happens it you save a new Illustrator file from within Illustrator directly onto the shared AFP volume?
Also, please share the contents of your afp.conf file!
…On Sat, Oct 28, 2023 at 2:11 AM, Jordi Sanfeliu ***@***.***(mailto:On Sat, Oct 28, 2023 at 2:11 AM, Jordi Sanfeliu <<a href=)> wrote:
Today appeared the following message repeated a lot of times, always with the same file name:
Oct 27 14:58:11 linux afpd[32451]: parse_entries: bogus eid: 9, off: 50, len: 3760
Oct 27 14:58:11 linux afpd[32451]: ad_header_read(/u/applepublic/xxx/231536/._Prop_2.ai): malformed AppleDouble
Oct 27 14:58:11 linux afpd[32451]: ad_header_read_osx(rfpath, ad, &st) failed: Input/output error
Oct 27 14:58:11 linux afpd[32451]: afp_openfork(Prop_2.ai): ad_open: Input/output error
I'll continue checking if the message appears with different file names.
—
Reply to this email directly, [view it on GitHub](#270 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAQCYM6EFVEZZLBLT5PEHZ3YBPTM5AVCNFSM6AAAAAAWTUNWRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTGI2DMNJZHE).
You are receiving this because you were assigned.Message ID: ***@***.***>
|
I don't know, I can't give you an answer now. I need to talk with people from the design department Monday.
|
On 10/27/23 19:11, Jordi Sanfeliu wrote:
ad_header_read_osx(rfpath, ad, &st) failed: Input/output error Oct 27
14:58:11 linux afpd[32451]: afp_openfork(Prop_2.ai): ad_open:
Input/output error |
can you please attach the AppleDouble file so we can take a look?
Thanks!
|
|
I guess the following patch should fix it. Can anyone test it? |
If you give me an RPM for a CentOS 7, I will install it and test it. |
@mikaku I created a test build on Copr: |
OK, I have now installed this one: Let's see how it works. Thanks! |
@mikaku Were you able to test this yet? |
@rdmark, yes, no new messages appeared so far after installing the 3.1.18-2 version. I'd like to wait a little more time because that past week there was some holidays and the company was not full of workers. So, if you don't mind let's wait a week more. |
No rush at all! Please take a week to gather more data. It's encouraging that you haven't seen any issues so far. FYI we're working towards a 3.2.0 release, which is at least several weeks out. |
@rdmark, So far I don't see any new message of type 'malformed AppleDouble' yet, but today I found 5 new messages like the following one:
Are those messages somehow related to the changes made in 3.1.18-2 version? |
@mikaku Would you be able to share the Also, are you seeing multiple warnings for the exact same file? I wonder if it gets converted to a compatible format later on. It is likely that the patch above is related, because we are now better at trying to parse macOS appledouble meta data, and don't error out like before. The question is whether the validation in |
Yes, that was in the beginning. During this week I saw similar messages for other files names. Also I've seen a message that I think didn't see before: Let me know if you need more information. |
Hi, just an update. I've not seen any new message of the type |
@mikaku Thanks for the update. Given the evidence, my hypothesis is that outdated osx style meta data created by the older version of netatalk have all been converted now. Is it fair to say that users of this AFP server were actively using it, creating files etc? Hopefully this would mean that macOS hasn't been creating meta data that netatalk couldn't parse. Anyhow, I put up a PR now with Ralph's patch. #575 |
Yep, I also think so.
Absolutely. I've just talked with some macOS users who write or create files in this AFP server and they have confirmed that they put new files, or modify existing ones in a daily basis. So it looks like good news. |
fwiw, this files were NOT created by Netatalk. These are files created by macOS itself when working on filesystems that don't support macOS metadata natively, like SMB without streams support. |
The patch has been merged to the main development branch. Please file a new issue ticket if you run into other suspicious logs in the future! |
Hello,
Following the recommendation of @knight-of-ni in #175, I opened new issue:
I'm seeing these messages:
Any idea?
OS: CentOS Linux release 7.9.2009 (Core)
The text was updated successfully, but these errors were encountered: