Neuer User posted on Thu, 01 May 2014 10:14:35 +0200 as excerpted: > It's probably best to copy al my data to another disk, then delete the > parttiion and make a new ext4 partition. btrfs is probably still too > experimental, I guess. I thought I replied to this one but it was to a different, similar problem, post. The blocked task bug isn't entirely uncommon, and is apparently a number of bugs with similar symptoms. One thing the devs have been requesting on such reports is the output from a sysrq-w, which dumps the blocked tasks so the devs can trace where the blocks are happening and fix the bugs. Either alt-sysrq-w, if you're running direct on hardware, or echo w > /proc/sysrq-trigger, which should work in VMs, etc, as well. But you're correct, tracking down and fixing all these bugs is likely to take awhile, and if you simply want something that works and don't have the luxury of testing and waiting for fixes, switching back to ext4 or whatever, until btrfs has matured a bit longer, would be the recommended course of action. And one more comment, a hint for next time. On mailing lists it's common to quote what you're replying to and reply below it. Top posting the reply works for that post, but messes things up for others trying to reply to the thread as well and for later readers, since now there's either a mixture of top-posted and in-context-posted replies at multiple levels or people end up omitting entirely the second level and deeper quotes that might have put the whole thing in context. Either case makes the thread difficult to follow or to properly reply to. =:^( -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
