On 11.02.20 г. 23:40 ч., Josef Bacik wrote: > If we're allocating a logged extent we attempt to insert an extent > record for the file extent directly. We increase > space_info->bytes_reserved, because the extent entry addition will call > btrfs_update_block_group(), which will convert the ->bytes_reserved to > ->bytes_used. However if we fail at any point while inserting the > extent entry we will bail and leave space on ->bytes_reserved, which > will trigger a WARN_ON() on umount. Fix this by pinning the space if we > fail to insert, which is what happens in every other failure case that > involves adding the extent entry. > > Signed-off-by: Josef Bacik <josef@xxxxxxxxxxxxxx> Reviewed-by: Nikolay Borisov <nborisov@xxxxxxxx>
