Skip to content
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.

Sign up for GitHub

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

Jump to bottom

posix_fallocate() failed: Operation not supported on transport endpoint #6349

Closed
N3TC4T opened this issue Jan 3, 2024 · 2 comments · Fixed by realm/realm-core#7251
Closed

posix_fallocate() failed: Operation not supported on transport endpoint #6349

N3TC4T opened this issue Jan 3, 2024 · 2 comments · Fixed by realm/realm-core#7251
Labels
Encryption:On Frequency:Always O-Community Repro:Always SDK-Use:Local T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed

Comments

@N3TC4T
Copy link

N3TC4T commented Jan 3, 2024 •
edited by sync-by-unito bot
Loading

How frequently does the bug occur?

Always

Description

Using realm inside Samsung secure folder will cause the app to crash with the message:

posix_fallocate() failed: Operation not supported on transport endpoint: Operation not supported on transport endpoint (95)

This happened after upgrading realm from v11.10.2 to v12.2.0, I believe multiple processes support for realm encryption added in v12 is the cause of this issue.

I see a duplicated issue in realm/realm-dotnet#3482 as well.

What services are you using?

Local Database only - using encryption

Platform OS and version(s)

Android - Galaxy S9 MOD. SM-G9600
@N3TC4T N3TC4T added the T-Bug label Jan 3, 2024
@kneth
Copy link
Contributor

kneth commented Jan 3, 2024

@N3TC4T Thank you for reporting

We will bring it up with our Realm Core team as it sounds like an issue deep down in our core database.

@sync-by-unito sync-by-unito bot added the Waiting-For-Reporter Waiting for more information from the reporter before we can proceed label Jan 3, 2024
@ironage ironage mentioned this issue Jan 11, 2024
Merged
4 tasks
@kneth
Copy link
Contributor

kneth commented Jan 29, 2024

@N3TC4T A fix is released in v12.6.0.

@RomainGF RomainGF mentioned this issue Feb 2, 2024
Closed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Encryption:On Frequency:Always O-Community Repro:Always SDK-Use:Local T-Bug Waiting-For-Reporter Waiting for more information from the reporter before we can proceed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fallback to manually consume space if posix_fallocate isn't supported at runtime realm/realm-core
2 participants
@kneth @N3TC4T