Helmut Hullen wrote: > If the value of "available" is unresolvable then btrfs should not > show any value. Disagree strongly. I think a pessimistic estimate would be much better to show, than no value at all. This may be what is currently shown. As for solving this with a high degree of usability, that's not really possible when constrained to the traditional paradigm that one filesystem will have completely consistent behavior backing all of it. I think the only answer is to have btrfs-specific tools that know more about the filesystem, and can present the relevant facts. Taking the example of part fs being raid0 and part being raid5, such a tool would then list calculated values for both those parts of the fs. One showing how much could go into the raid0 part, the other how much could go into the raid5 part. But for such filesystems, Linux can't do what Helmut would like. Maybe it would be possible to optimize the reported numbers, to be what the user actually wants as often as possible. Ie. if there is only one type of backing storage (sorry, don't know the terms) then the calculation would be easier to get right, following the simple formula that was just given. This is all eye candy however, completely irrelevant IMO as long as the filesystem oopses, or eats root nodes. :) //Peter -- 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
