Description of problem: I was trying to see, if we are logging somewhere about the successful operatoin about a quota limit setting on "/" or subdir, could not find it and hence putting up the bug Version-Release number of selected component (if applicable): glusterfs-3.4.0.34rhs-1.el6rhs.x86_64
(In reply to Saurabh from comment #0) > Description of problem: > > I was trying to see, if we are logging somewhere about the successful > operatoin about a quota limit setting on "/" or subdir, could not find it > and hence putting up the bug > > Version-Release number of selected component (if applicable): > glusterfs-3.4.0.34rhs-1.el6rhs.x86_64 Hi Saurabh, In the cmd_history.log, we are logging about the successful operation of quota limit setting on a directory. [2015-07-08 06:01:06.678153] : v quota vol1 limit-usage /dir/test/ 4MB 80 : SUCCESS [2015-07-08 07:15:59.117990] : v quota vol1 limit-usage /dir/test/ 5MB 70% : SUCCESS Is it necessary to log it somewhere else too?
The bug is already fixed in the latest version. Logs for the successful operation of setting quota limit in a directory can be found in cmd_history.log.
Closing this bug since it is already fixed. [2015-07-08 06:01:06.678153] : v quota vol1 limit-usage /dir/test/ 4MB 80 : SUCCESS [2015-07-08 07:15:59.117990] : v quota vol1 limit-usage /dir/test/ 5MB 70% : SUCCESS
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days