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

ENOTSUP when using noobaa pv-pool with AWS EFS storage class due to xattr not supported #7843

Closed

jackyalbo opened this issue Feb 22, 2024 · 0 comments · Fixed by #8005

Assignees

Contributor

jackyalbo commented Feb 22, 2024

Environment info

NooBaa Version: master
Platform: OpenShift AWS

Actual behavior

when we upload a file to a pv-pool we currently save the metadata as xattr attached to the file this can be problematic when using storage classes that don't support xattr like AWS EFS

Expected behavior

we should understand that xattr are not supported by the storage and failback to using 1 file for data and a second for metadata as we did in older versions

Steps to reproduce

install ocp in AWS
install noobaa with storage class set to AWS EFS: efs-nfs-client and try to create a pv-pool backingstore
see that backingstore pod is constantly failing with ENOTSUP

More information - Screenshots / Logs / Other output

tangledbytes self-assigned this

tangledbytes mentioned this issue

Fix ENOTSUP by falling back to meta files #8005

Merged

2 tasks

tangledbytes closed this as completed in #8005

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment