I have this problem with 1.0.7 on a production system.
using ch.qos.logback.core.rolling.TimeBasedRollingPolicy with ch.qos.logback.core.rolling.TimeBasedRollingPolicy and ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP

There are rather small files.

app.2013-01-20.0.gz │ 226│Jan 21 01:05
app.2013-01-21.0.gz │ 518│Jan 22 07:09
app.2013-01-22.0.gz │ 1680│Jan 23 07:57
app.log │ 12435│Jan 23 14:03
app.log15076690229815042.tmp │ 51099│Jan 11 23:20
app.log15266797381668132.tmp │ 30762│Jan 12 20:46
app.log15336808959623682.tmp │ 17776│Jan 14 23:55
app.log15513758335467184.tmp │ 57529│Jan 15 23:33
app.log15617889856650857.tmp │ 17012│Jan 16 23:49
app.log15683275300086270.tmp │ 140223│Jan 18 22:34
app.log15868486690508416.tmp │ 10589│Jan 19 22:46
app.log15943696438353616.tmp │ 2817│Jan 21 11:50
app.log16051971617579252.tmp │ 3040│Jan 21 23:57
app.log16141217076917693.tmp │ 11745│Jan 22 22:21

On the development machine, it works ok.
both machine has:
java: jdk1.6.0_24
tomcat: apache-tomcat-6.0.26

the "only" difference is the kernel version:

production:
uname -a
Linux production 2.6.32.7-grsec #4 SMP Mon Feb 8 19:59:41 CET 2010 x86_64 GNU/Linux

development:
uname -a
Linux development 3.2.7 #1 SMP Fri Feb 24 19:18:18 CET 2012 x86_64 GNU/Linux

what should cause the problem?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira