On Tue, Jan 09, 2018 at 06:04:05PM +0200, Nikolay Borisov wrote: > Currently when df (resp. statfs) is executed on a btrfs instance the > free space is calculated as the freespace of the block groups + > any unallocated space on the devices, constituting this filesystem. > There is a catch, however, in that the unallocated space from the > devices has 1 mb subtracted from each device to closely follow btrfs' > allocator behavior. This is all good except that when we have a file > system and the system chunk's allocation profile is single (as is the > default in mixed mode) it occupies the range 0..4mb and thus implicitly > prevents allocation starting in the range 0..1mb. In those cases > additionally subtracting 1mb during statfs makes us misreport the > actual free space and this causes generic/015 to fail. > > Signed-off-by: Nikolay Borisov <nborisov@xxxxxxxx> This is fine by me, Reviewed-by: Josef Bacik <jbacik@xxxxxx> Thanks, Josef -- 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
