Szalma László posted on Wed, 28 Oct 2015 09:44:12 +0100 as excerpted: > The umount/mount ALWAYS solved the problem for me, mount -o remount,ro > was tried for the first time, but it was not enought. Reboot was not > needed. > (kernel 4.2.4) So that means it's filesystem state that's tracked thru a remount, not something like deleted/orphan files that a remount should square away. But a full unmount clears the state, without having to unload the btrfs kernel module or reboot. Which at least limits the active zone of the problem. Unfortunately, I'm not a dev and don't have a clue where to go from there... unless it's related to the recent delayed-refs bug, in which case I believe a late 4.3 rc, or 4.3.0 when released, should fix it. That fix should be CCed to stable and thus appear there eventually, but I normally track pre- releases, not stable, so don't know how long it might be... And again, I don't know it's even related, but it does appear to be the active bug of the moment, so in the absence of knowing, one can hope. -- 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
