Bug 1029443 - quota: for pre-existing data, the alerts(soft-limit) are not found in logs
Summary: quota: for pre-existing data, the alerts(soft-limit) are not found in logs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: quota
Version: 2.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1202289 1265532
TreeView+ depends on / blocked
 
Reported: 2013-11-12 12:02 UTC by Saurabh
Modified: 2016-09-17 12:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1202289 (view as bug list)
Environment:
Last Closed: 2015-11-17 08:52:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Saurabh 2013-11-12 12:02:14 UTC
Description of problem:
Could not see the alert messages in the intended logs.
This issue is seen with pre-existing data and then setting quota limit on that directory.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.43rhs-1

How reproducible:
always

Steps to Reproduce:
1. create a volume, start the volume, enable quota
2. mount over nfs or glusterfs
3. mkdir dir
4. create data inside the dir, say upto 100GB
5. set quota limit on dir, say 100GB its

Actual results:
alert message about soft-limit is not seen in the logs.


Expected results:
alerts should be generated if limit crosses the soft-limit %age

Additional info:
Though after limit is reached and trying to create more data, sends disk quota exceeded

Comment 2 Vijaikumar Mallikarjuna 2015-03-16 10:05:40 UTC
Testcase ./tests/bugs/quota/bug-1087198.t is failing because sometimes 'Usage crossed soft limit' alert message is not generated in the log.

Comment 3 Vijaikumar Mallikarjuna 2015-08-06 10:07:31 UTC
This is an expected behavior, as alert logs are generated only when there is an IO happening.
For a existing data, when quota is enabled, alert logs will not be generated if the existing data already crossed quota limit.

Comment 4 Vijaikumar Mallikarjuna 2015-11-17 08:52:50 UTC
This is an expected behavior, so closing bug.


Note You need to log in before you can comment on or make changes to this bug.