> Am Sonntag, 7. Dezember 2014, 10:20:27 schrieb ashf...@whisperpc.com: >> Martin, >> >> > I read that the actual >> > what is free is unknown. And there are several reasons for that: >> > >> > 1) On a compressed filesystem you cannot know, but only estimate the >> > compression ratio for future data. >> >> It is NOT the job of BTRFS, or ANY file-system, to try to prodict the >> future. The future is unknown. Don't try to account for it. When >> asked >> for the status (i.e. 'df'), it should return the current status. >> >> > 2) On a compressed filesystem you can choose to have parts of it >> > uncompressed by file / directory attributes, I think. BTRFS can't >> > know how much of the >> > future data you are going to store compressed or uncompressed. >> >> Same as above. > > What is the point you are trying to make? > > I just described the reasons on what problems there are with trying to > predict > available free space, with BTRFS as an example. Some points apply to all > filesystems, some do not, so what is the point you are trying to make?
My point is that you don't try to predict, as that's a guaranteed path to failure. You deliver what you know. This is what every other file-system does. There's no reason to do anything else. Peter Ashford -- 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
