On 12/14/2011 10:46 AM, Josef Bacik wrote:
file looks like its only 50m but still has 100g of extents taking up space orphan cleanup happens and the inode is truncated and the extra space is cleaned up
Yes, but isn't the only reason that the i_size change actually hit the disk is because of the orphan item? So with no orphan item, the i_size remains at 100g.
-- 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
