Alisa Martirosyan created LOGBACK-1431: ------------------------------------------ Summary: SizeBasedTriggeringPolicy and FixedWindowRollingPolicy : file grows enormously in some cases Key: LOGBACK-1431 URL: https://jira.qos.ch/browse/LOGBACK-1431 Project: logback Issue Type: Bug Components: logback-classic, logback-core Affects Versions: 1.2.3 Environment:   Logback 1.2.3,  RHEL 6   Reporter: Alisa Martirosyan Assignee: Logback dev list Hi there,  Using logback 1.2.3. We have SizeBased and FixedWindow policy described as follows:    <appender name="METRICS" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>\{filename}</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>\{filename}.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>9</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>20MB</maxFileSize> </triggeringPolicy> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="com.avaya.ept.common.logging.layout.CLFLayout"> <pattern>|%thread|%level|%logger\{15}|%msg%n</pattern> </layout> </encoder> </appender>   Recently we've faced the issue when log file \{filename}-1.log grows to the enormous size of 40gb without any particular reason. After removing this log and restarting the application log continues to rotate normally, on ~20mb size mark.  We could not analyze the logs as they causes the system to freeze (due to lack of free disk space) and had to be removed ASAP. Is there any particular reason why this could be happen?  Using RHEL 6.  -- This message was sent by Atlassian JIRA (v7.3.1#73012)