• J
    Btrfs: handle not finding the extent exactly when logging changed extents · 0aa4a17d
    Josef Bacik 提交于
    I started hitting warnings when running xfstest 68 in a loop because there
    were EM's that were not lined up properly with the physical extents.  This
    is ok, if we do something like punch a hole or write to a preallocated space
    or something like that we can have an EM that doesn't cover the entire
    physical extent.  So fix the tree logging stuff to cope with this case so we
    don't just commit the transaction.  With this patch I no longer see the
    warnings from the tree logging code.  Thanks,
    Signed-off-by: NJosef Bacik <jbacik@fusionio.com>
    0aa4a17d
tree-log.c 93.6 KB