On 2020/1/29 下午5:23, Nikolay Borisov wrote: > > > On 29.01.20 г. 7:19 ч., Qu WenRuo wrote: >> Hi David, >> >> Mind to merge the patchset for misc-next? >> >> As patches 1~4 are reviewed, and the last patch is not that complex to >> grasp, I guess it's time to finish the long existing df 0 space bug, >> with better RAID5/6 estimation for df. >> >> >> For the long discussion about whether we should set available space back >> to 0 when metadata is exhausting, I still tend not to do so, since >> metadata and data are separate resources. > > Be that as it may users shouldn't really care about the distinction > between metadata/data space. What they should care is whether they can > create any new files, if metadata is exhausted they can't. As I mentioned, other fs has their own limitation too. E.g the inode number limitation for xfs/ext4. And they report their limit with other mechanism (as df supports it), but not blindly report 0 available. BTW aren't there reports of free data space but no meta space and df still reports available space? That 0 available space mechanism only get triggered when things go wrong, not making much real benefit to the end user. Thanks, Qu > > >> >> Thanks, >> Qu >>
