Hi, I'm getting "blocked for more than 120 seconds" messages too.
In my case, it is for a simple RAID1 volume that is rebuilding for the first time (new volume), whilst mounted as a LUKS crypt volume and writing /dev/zero before actual deployment. I am running a stock Wheezy kernel: ~ # uname -a Linux n4800eco-a 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux As I am deliberately NOT running btrfs, the common link may be mdadm or LUKS. I'm also noticing btrfs modules being loaded on another box, even though I am not at all ready to trust btrfs for any file system at this time. There may be some bug with mdadm/crypt(LUKS)/btrfs -- or it may have nothing to do with btrfs. My problem almost certainly isn't btrfs unless there is some kernel code giving me grief without loading the btrfs module. More details of my problem: https://lists.debian.org/debian-user/2014/06/msg00070.html NB: working through my problem in a dropbear busybox environment that hasn't loaded btrfs module. The kernel is the same as the /normal/ system, compliments of mkinitramfs tool.... Cheers A. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
