Bug 799267 - clear-locks on a volume generates separate log files every time it is executed
Summary: clear-locks on a volume generates separate log files every time it is executed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-03-02 10:26 UTC by Shwetha Panduranga
Modified: 2015-11-03 23:04 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:44:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shwetha Panduranga 2012-03-02 10:26:53 UTC
Description of problem:
It would be good if the logs are appended to a single file when clear-locks on a volume is executed. Currently, clear-locks creates separate log files for the same volume.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
often

Comment 1 Anand Avati 2012-03-07 18:47:57 UTC
CHANGE: http://review.gluster.com/2861 (glusterd: Append internal mount logs of clear-locks command to a single file) merged in master by Vijay Bellur (vijay)

Comment 2 Shwetha Panduranga 2012-05-04 04:43:51 UTC
Bug is fixed . verified on 3.3.0qa39


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