A few days ago, I added a 500GB drive to my RAID0 of two 1TB drives. I then ran sudo btrfs fi balance start -dconvert=single . after two minutes, my PC hung, not even SysRq worked. I rebooted, ran sudo mount /mnt/backup which hung for a few minutes and then hang my PC again completely (SysReq not working) Next day mounting worked, but some minutes later it panicked again. On one of these, I had this message in kernel log afterwards: kernel: ------------[ cut here ]------------ kernel: kernel BUG at fs/btrfs/extent-tree.c:1833! (thats all) on another occasion, I left `dmesg -w` open and took this photo: http://i.imgur.com/Qemzlr9.png but the stack trace is cut off I also have some of these in my logs from when mounting/unmounting hung for longer times: http://i.imgur.com/I8moyYG.png At some point, I upgraded my kernel from 4.1.6 to Linux 4.2.1-1-ARCH #1 SMP PREEMPT Tue Sep 22 06:57:07 CEST 2015 x86_64 GNU/Linux and btrfs-progs v4.2.1 but panics still happened afterwards. I also tried mounting with `mount /mnt/backup -o skip_balance` but that took 2 minutes and resulted in the same kernel panic. Now I tried to reproduce to get the full stack trace, but it did not kernel panic this time, instead I got this: http://sprunge.us/cACT crash, afterwards the drive is mounted readonly. What can I do? -- 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
