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.

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

Logmessage: Error: Librados obj: a9cd162ed243bf5b8f150000c86de11e, could not be removed #203

Closed
jrse opened this issue Oct 11, 2018 · 1 comment
Assignees

Comments

@jrse
Copy link
Contributor

jrse commented Oct 11, 2018

In case the backup of a users mail fails, due to an invalid read of a source mail (invalid size / corrupt data),
the copy from mdbox->rbox terminates.

In this case, a log message like;
Error: Librados obj: a9cd162ed243bf5b8f150000c86de11e, could not be removed
will be written to the log file.

In this case the message is misleading, because the object was not written to the ceph storage.

possible solutions:

  1. do a additional stat before the ceph delete (cleanup)
  2. remember, if a ceph-write was called for this object.
@jrse jrse changed the title Logmessages: Error: Librados obj: a9cd162ed243bf5b8f150000c86de11e, could not be removed Logmessage: Error: Librados obj: a9cd162ed243bf5b8f150000c86de11e, could not be removed Oct 11, 2018
@jrse jrse self-assigned this Oct 17, 2018
@jrse
Copy link
Contributor Author

jrse commented Oct 17, 2018

if delete returns with ENOENT no error will be written to log file.

@jrse jrse closed this as completed Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant