Hide Forgot
Description of problem: min-free-disk is not giving "no space left on the device" error on crossing min-free-disk value in all bricks Version-Release number of selected component (if applicable): RHGS 3.1.3 How reproducible: Always Steps to Reproduce: 1. create a distributed volume 2. Keep min free disk defualt / set it with a different value 3. Try to fill up the volume. Even if the min-free-disk value is crossed, Not getting the no space left on the device error or any warning on the console. Actual results: Even if the min-free-disk value is crossed, Not getting the no space left on the device error or any warning on the console. Expected results: min-free-disk should prevent the bricks from filling up to 100% Additional info:
This is behaving as expected - nowhere do we state that min-free-disk will return enospc. The min-free-disk setting does not restrict creates or writes, it just tries to keep that much of the disk free. I am closing this BZ as notabug. If there are issues with disks filling up, please file a separate bug with more details.
To add to this: { .key = {"min-free-disk"}, .type = GF_OPTION_TYPE_PERCENT_OR_SIZET, .default_value = "10%", .description = "Percentage/Size of disk space, after which the " "process starts balancing out the cluster, and logs will appear " "in log files", },
(In reply to Nithya Balachandran from comment #3) > To add to this: > > { .key = {"min-free-disk"}, > .type = GF_OPTION_TYPE_PERCENT_OR_SIZET, > .default_value = "10%", > .description = "Percentage/Size of disk space, after which the " > "process starts balancing out the cluster, and logs will appear " > "in log files", > }, Hi Nithya, Thanks for your comments. Will it be possible to display the warning message in the console? Just like quota warning messages Regards Riyas
We can send an event. However, this BZ as such is not valid as this is not the expected min-free-disk behaviour which is why I closed it. Please file a different BZ for the space issue.