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

properly report full filsystem errors #183

Open

PerilousApricot opened this issue Jan 2, 2019 · 0 comments

Member

PerilousApricot commented Jan 2, 2019

When lstore fills up, writes/closes on a full filesystem returns a generic error code, when something like ENOSPACE would be more appropriate.

In addition, the FUSE interface fails silently and returns no errors at all.

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