Bug 1019302 - quota: event exceeding hard limit is not getting logged
Summary: quota: event exceeding hard limit is not getting logged
Keywords:
Status: CLOSED DUPLICATE of bug 1020816
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.1
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Anuradha
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-15 12:51 UTC by Saurabh
Modified: 2016-09-20 02:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-30 07:31:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Saurabh 2013-10-15 12:51:31 UTC
Description of problem:
event exceeding hard limit is not getting logged,

this is just related to Hard Limit, should be in similar fashion as in soft-limit.

As, after the quota hard limit is reached, in the brick logs we are mentioning any kind of info about quota limit reaching or crossing it.

Although we are sending EDQUOT to the application or logs like nfs.log but actually not a "A" or "W" in brick logs.

This is required in brick logs as such we are having quota translator in the bricks.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.34rhs-1.el6rhs.x86_64


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