-
Notifications
You must be signed in to change notification settings - Fork 27
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
Write a test to find out what happens when data low water is bigger than actual device #379
Comments
@mulkieran, device mapper seems to not care about the low water mark being too large. [gchin@to-be-determined stratis-storage]$ lsblk |
@waltdisgrace Can you display the thinpool's table, also? We want to check if the value was silently changed to another value, or not. My guess is that we'll find that the low water mark is as you set it. |
[gchin@to-be-determined devicemapper-rs]$ sudo dmsetup table thin1 |
So, now, how does it behave? We'll have to figure out how to explore this question. |
So, that devicemapper accepts a very large number does kind of make sense. That's a reasonable way for a client to indicate that it never wants to receive low-water related events. But there are two interesting questions.
|
We should set up a test to use inotify_wait to check for the event when the thinpool is suspended and resumed. |
We would like to know exactly what happens if we tell the thinpool that its low water mark is larger than the data device itself. This is a test that could probably be run well by setting up a thinpool, and then specifying the too-large low water mark. It is probably not necessary to set up any thin devices on the the thinpool for the test.
It is reasonably to try first using the command-line, i.e., dmsetup.
The text was updated successfully, but these errors were encountered: