Skip to content

eosfs: errors are not propagated correctly #4800

Description

@glpatcern

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.

Activity

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions