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

General error recovery/handling behavior #3

Open
natevw opened this issue Jun 1, 2014 · 0 comments
Open

General error recovery/handling behavior #3

natevw opened this issue Jun 1, 2014 · 0 comments

Comments

@natevw
Copy link
Owner

natevw commented Jun 1, 2014

When anything goes wrong, we basically just bubble it up the stack. But what state does this leave the on-disk structures? Or our in-memory structures vs. the on-disk ones?

When it made sense, I've usually taken care to do on-disk operations in the "safest" (i.e. most interruptible) order. But maybe not always, and there's also state like _fd.entry._size that could get mismatched.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant