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

eosfs: errors are not propagated correctly #4800

Open
glpatcern opened this issue Aug 6, 2024 · 0 comments
Open

eosfs: errors are not propagated correctly #4800

glpatcern opened this issue Aug 6, 2024 · 0 comments
Assignees
@glpatcern

Comments

@glpatcern
Copy link
Member

This at least applies to "quota exceeded" and "device or resource busy" because of locked files.

In both (and possibly other) cases, the error string is not even logged by reva, only a generic xrootd return code 54 is logged - which is translated to HTTP 500 for the user.
@glpatcern glpatcern self-assigned this Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@glpatcern glpatcern

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@glpatcern