Kent Overstreet <kmo@...> writes:
> > I just rebased bcache-3.10-stable and added the fix you tested to it. > > Also, HEAD in the bcache repository now points to bcache-3.10-stable and > not bcache-for-3.10. > > Can you run echo t > /proc/sysrq-trigger when things get stuck, and give > me the full dmesg output? > I have now tested with the latest git kernel. It has become better again, but the basic problem remains. The dmesg messages I send via e-mail root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 09:26:43 CEST 2013 /dev/bcache0 74G 1,7G 68G 3% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 09:28:09 CEST 2013 /dev/bcache0 74G 4,6G 65G 7% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 09:51:41 CEST 2013 /dev/bcache0 74G 11G 59G 16% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 09:56:05 CEST 2013 /dev/bcache0 74G 12G 59G 17% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 10:00:42 CEST 2013 /dev/bcache0 74G 12G 58G 17% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 10:03:58 CEST 2013 /dev/bcache0 74G 12G 58G 17% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 10:14:56 CEST 2013 /dev/bcache0 74G 13G 58G 18% /tmp/bcache root@server:/usr/src# date;df -h | grep bcache Do 19. Sep 10:39:14 CEST 2013 /dev/bcache0 74G 13G 57G 19% /tmp/bcache root@server:/usr/src# du -sh 14G . root@server:/usr/src# -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
