Mark Zealey posted on Mon, 04 Jan 2016 14:11:00 +0200 as excerpted: > Also I have quota tracking enabled on the btrfs volume if that makes any > difference. I'm not sure whether it makes a difference for this particular hang, but I do know that btrfs quotas are simply not stable thru at least 4.3. I'm not sure what 4.4 status is, but my general recommendation regarding btrfs quotas is... If you need quotas, use a more mature filesystem where they work reliably, if you don't, then turn them off for now, and don't turn them on again until at least two complete kernel cycles have passed without a known quota bug or instability, which, if 4.4 is indeed known-bug-free and it and 4.5 remain so thru 4.6, means that would be the earliest I could recommend turning it on, and that's only if there's no known quota bugs in 4.4 or 4.5 or 4.6 by the time of 4.6 release. Unless of course you're deliberately and specifically testing btrfs quotas and working with the devs on fixing quota specific issues, in which case, thank you. =:^) Meanwhile, the rather long history of problems with quotas on btrfs is both the reason I'm suggesting two complete cycles without quota issues before enabling them, and a good reason to be skeptical as to current releases' quota code or the likelihood of that two-releases-quota-bug- free happening any time soon. There's definitely a lot of work going into the feature and there's gotta be a point where it actually works, but they've rewritten the code three times and are still dealing with bugs, and it has been in a "try back in a couple kernel cycles" state for years, now, so... who knows? Kinda reminds me of how long the raid56 code took, only quota was being worked on before that, and is still being worked on, so... -- 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
