Hello, I've been following this list for years and I see during various situations this message coming up. Some times it's a genuine problem that there is actually not enough space. In other cases it's some by-product of something else. I have seen this error personality on a broken system ( which I never figured out what had happened). I know this is still experimental but I just want to make sure my expectations are not really out on sync with the others.
As an end user when I see an error like this the first thing I will do is check the space (using 'df' command) [1]. If I see more that 7% I usually think it's OK, (depends on the size of partition as well). - Is this unreasonable in btrfs filesystem? Is there a formula to calculate how much space btrfs _might_ need? - It's probably not your job but can df reports correct sizes for btrfs? I've seen some threads on trying to show the actual space occupied by data and/or metadata with btrfs command. Can we expect this someone to be incorporated into df command? - In cases that btrfs reports this error but there's something else that's causing it, can we expect better error handling from btrfs so the end user is pointed to the correct direction? [1]: one could argue that an end user should use the btrfs commands instead but let's leave that for now. Apologies if these have already been answered or are already on roadmap. Thanks in advanced, your comments are appreciated. Kind regards, Leonidas -- 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