On Mon, Sep 18, 2017 at 11:20 AM, Tomasz Chmielewski <mangoo@xxxxxxxx> wrote: >>> # df -h /var/lib/lxd >>> >>> FWIW, standard (aka util-linux) df is effectively useless in a situation >>> such as this, as it really doesn't give you the information you need (it >>> can say you have lots of space available, but if btrfs has all of it >>> allocated into chunks, even if the chunks have space in them still, there >>> can be problems). > > > I see here on RAID-1, "df -h" it shows pretty much the same amount of free > space as "btrfs fi show": > > - "df -h" shows 105G free > - "btrfs fi show" says: Free (estimated): 104.28GiB (min: > 104.28GiB) > I think both use the same algorithm to compute free space (df at the end just shows what kernel returns). The problem is that this algorithm itself is just approximation in general case. For uniform RAID1 profile it should be correct though. -- 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
