I can confirm this issue. (using logback version 1.2.3)

We have totalSizeCap set to 5GB and maxFileSize set to 512MB in combination with SizeAndTimeBasedRollingPolicy. When a sudden burst in amount of logs happened, we've got 7-8GB archived logs and it exhausted available disk space on the /var partition. The rolling policy just kept the oldest archived logs intact, and more - it didn't count their size towards the total size of archived logs.

The fix to the issue seems so easy – just replace

offset < maxHistory

with

offset <= maxHistory
// or
offset < maxHistory + 1

whichever suits the code style of the project most.

Why is this still unresolved?