-
Notifications
You must be signed in to change notification settings - Fork 44
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
Volume is not becoming readonly when the space is completely exhausted #36
Comments
@somesh2905 just try to write IO's on the same volume. kernel will mark the fs to RO if IO's will fail. Have you tried to write more than the given size? |
Yes, writing IO's on same volume should work.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What Happened
Provisioned Jiva volume using CSI provisioner and mounted it on busybox application. Filled the space completely but volume did not enter to RO state. (for file-system ext4 and xfs)
What to expect
Volume should go in RO state after complete space exhaustion
The text was updated successfully, but these errors were encountered: