Frédéric Grelot posted on Sun, 08 Nov 2015 07:45:39 +0100 as excerpted: > After 8 hours, "btrfs check --readonly" is still "checking quota > groups". It does not have any IO activity, but uses 100% CPU. > #top > 1143 root 20 0 2266596 2.148g 1124 R 100.0 56.0 183:37.14 > btrfs check --readonly /dev/sda1 > > I am not sure what to do : if you have no idea, since I have less than > 3Tb of data I will just manually degrade the volume by removing one of > the disk, build a new btrfs on it, copy the data since I can still open > the old one RO, then manually take devices from the old volume to new > new one (converting to raid1 first, then raid6). Ahh... quotas. Devs are working very hard on them, but to this point quotas have never really worked /correctly/, and the estimate as to when they might... seems to always remain a couple kernel cycles out. So my recommendation continues to be, either you really need quotas and thus should use a filesystem where they are known to be mature and stable, or you don't, and btrfs is an option, but don't enable quotas and avoid the problems they cause. Unless of course you're specifically working with the devs to debug and fix current functionality and don't mind loosing a filesystem or two in the process as a result, in which case, THANK YOU for helping to stabilize the feature for everyone, however long it might take. As for when it might be safe to enable them, at this point, with the quota history we have, I'd suggest waiting at least two kernel cycles after all known quota issues have been fixed. But whether that's 4.6 or 5.6 (with roughly 5 releases per year and a assuming another major version bump at what would be .20, in keeping with the precedent set with the 3.x series, it's roughly two years per major version kernel cycle, so 5.6 would be around 1Q2018) or 6.6... who can tell, until it happens? -- 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
