Red Hat Bugzilla – Bug 1018205
quota: change the values of soft-timeout and hard-timeout and there is not "A" message reported
Last modified: 2016-09-19 22:00:07 EDT
Description of problem:
No "A" message reported after crossing the soft-limit
Seen this issue after changing the values for soft-timeout and hard-timeout.
As, before the above mentioned change I had an "A" message.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a volume, start it
2. enable quota and set limit as 1GB for "/"
3. change the soft-timeout and hard-timeout values
Volume Name: dist-rep3
Volume ID: 75ce853a-fa9c-442e-9705-4408535ab9be
Number of Bricks: 6 x 2 = 12
4. mount over nfs
5. start creating data till quota limit is not reached.
no "A" based on this test.
after reaching the soft-limit, "A" message is expected.
There are two "alert messages" :-
A1. one string says "Usage crossed above soft-limit":- comes just the moment default soft-limit is crossed (i.e. 80%)
A2. other one is "Usage above soft-limit":- comes on the basis of write to a brick.
Now, in this bug I have said there is no "A" message , basically "A" represents alert. Effectively, if the argument is that alert may not have because the write would just surpassed the time that the alert was suppose to come, if this is the case I presume we may miss A1, but what about A2.
Patch for review for rhs-2.1 posted on :
Patch for review for rhs-2.1-u1 posted on :
Moving the known issues to Doc team, to be documented in release notes for U1
I've documented this as a known issue in the Big Bend Update 1 Release Notes. Here is the link: