On Thu, Aug 4, 2016 at 10:53 AM, Lutz Vieweg <l...@5t9.de> wrote: > The amount of threads on "lost or unused free space" without resolutions > in the btrfs mailing list archive is really frightening. If these > symptoms commonly re-appear with no fix in sight, I'm afraid I'll have > to either resort to using XFS (with ugly block-device based snapshots > for backup) or try my luck with OpenZFS :-(
Keep in mind the list is rather self-selecting for problems. People who aren't having problems are unlikely to post their non-problems to the list. It'll be interesting to see what other suggestions you get, but I see it as basically three options in order of increasing risk+effort. a. Try the clear_cache mount option (one time) and let the file system stay mounted so the cache is recreated. If the problem happens soon after again, try nospace_cache. This might buy you time before 4.8 is out, which has a bunch of new enospc code in it. b. Recreate the file system. For reasons not well understood, some file systems just get stuck in this state with bogus enospc claims. c. Take some risk and use 4.8 rc1 once it's out. Just make sure to keep backups. I have no idea to what degree the new enospc code can help well used existing systems already having enospc issues, vs the code prevents the problem from happening in the first place. So you may end up at b. anyway. -- Chris Murphy -- 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
