Tobias Holst posted on Thu, 07 Aug 2014 17:12:17 +0200 as excerpted: > Is there anything new on this topic? I am using Ubuntu 14.04.1 and > experiencing the same problem. > - 6 HDDs - LUKS on every HDD - btrfs RAID6 over this 6 crypt-devices No > LVM, no nodatacow files. > Mount-options: defaults,compress-force=lzo,space_cache With the original > 3.13-kernel (3.13.0-32-generic) it is working fine.
I see you're using compress-force. See the recent replies to the "Btrfs: fix compressed write corruption on enospc" thread. I'm not /sure/ your case is directly related (tho the kworker code is pretty new and 3.13 may be working for you due to being before the migration to kworkers, supporting the case of it being either the same problem or another related to it), but that's certainly one problem they've recently traced down... to a bug in the kworker threads code, that starts a new worker that can race with the first instead of obeying a flag that says keep it on the first worker. Looks like they're doing patch that takes a slower but safer path to work around the kworker bug for now, as that bug was just traced (there was another bug, with a patch available originally hiding the ultimate problem, but obviously that's only half the fix as it simply revealed another bug underneath) and fixing it properly is likely to take some time. Now that it's basically traced the workaround patch should be published on-list shortly and should make it into 3.17 and back into the stables, altho I'm not sure it'll make it into 3.16.1, etc. But there's certainly progress. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
