Hi Chris, I set dmesg -n7 and didn't see anything extra logged (I had to use sudo to enable it. I am not familiar with sysrq-w and sysrq-t, however you ask "while it is locked", this is a "real" hard lock. everything is unresponsive and the machine even fails to respond to ping request. It happened again over night and again the only clues where the btrfs-transaction and btrfs-flush_del going ballistic. Regards Sean Clarke --------------------------------------------- SEC Consulting Limited Phone: +44 (0)23 8040 5599 Website: http://www.sec-consulting.co.uk Email: sean.clarke@xxxxxxxxxxxxxxxxxxxx On Thu, Oct 24, 2013 at 9:47 AM, Chris Mason <chris.mason@xxxxxxxxxxxx> wrote: > Quoting Sean Clarke (2013-10-23 15:26:15) >> Hi, >> I have an Intel Core i7 based fileserver with 18TB BTRFS in a 6x >> 3TB RAID 1+0 configuration. The system was working fine running Ubuntu >> 13.04 (kernel 3.11.0-12-generic). The system was upgraded to Ubuntu >> 13.10 (kernel 3.11) and began to lock up daily, sometimes every couple >> of hours. Previously it never crashed and was only taken down for >> maintenance so a bug was files on launchpad >> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1237794). > > Does your kernel config include the softlockup detector? If you could > please do sysrq-w and sysrq-t while it is locked, it'll help us track it > down. > > It will be much easier if you have a serial console or network console, > and you've increased your kernel logging level to the highest value > (dmesg -n7) > > -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
