On Tue, Nov 20, 2018 at 08:04:58AM +1100, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > Just tried to punch a 40T sparse file when enospc was triggered due > to extent size hints consuming more space than expected. It failed > with: > > # sudo xfs_io -c "fpunch 0 40t" /mnt/fast/xfs-arekm.img > fallocate: No space left on device > # > > because the writeback error of ENOSPC was being reported. We're > going to free that space, so we don't care if there was a ENOSPC > writeback error. So ignore ENOSPC errors and punch anyway. How do even get -ENOSPC back from writeback? It seems like we have a much worse root cause lingering here.
