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

Volume is not becoming readonly when the space is completely exhausted #36

Open
somesh2905 opened this issue Feb 10, 2020 · 2 comments
Open
Assignees

Comments

@somesh2905
Copy link
Contributor

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)

/dev/sdc                 12.0G     12.0G     40.0K 100% /busybox
/dev/sdc on /busybox type xfs (rw,relatime,attr2,inode64,noquota)

What to expect
Volume should go in RO state after complete space exhaustion

@utkarshmani1997 utkarshmani1997 self-assigned this Feb 10, 2020
@utkarshmani1997
Copy link
Contributor

utkarshmani1997 commented Feb 10, 2020

@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?
Please share the output of du -sh and df -h as well.
cc: @gprasath

@kmova kmova transferred this issue from openebs-archive/jiva-csi Feb 7, 2021
@mb7079
Copy link

mb7079 commented Sep 30, 2021

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants