On Wed, Nov 01, 2017 at 01:51:59PM +0100, Carlos Maiolino wrote: > Hi, > > Does anyone know how fallocate should behave if it hits an ENOSPC in the middle > of the block reservation? The man page is not really specific about it. > > Being more specific: > > If we try to fallocate a 10G file, but the filesystem does not have enough space > to accommodate the whole allocation request, it will return an ENOSPC, but, it > doesn't specifically says if the whole allocation should fail or if we can end > up with a partially allocation. > > In the man page: > > "After a successful call, subsequent writes into the range specified by offset > and len are guaranteed not to fail because of lack of disk space." > > and: > > "ENOSPC There is not enough space left on the device containing the file > referred to by fd." > > By my interpretation, I'd say that if the fallocate fails with -ENOSPC, no > allocation should be done at all, and the file size should not be changed, > once we can't guarantee the writes will not fail due lack of disk space. preallocation can fail half way through, but users can't see that so there's no real requirement to remove partial allocations on failure. Indeed, rollback of partial allocations makes error handling ridiculously complex - think about an allocation across a range of a file that has alternating holes and unwritten extents. Half way through we get ENOSPC, and now we have to go punch out the extents we've already preallocated. Unless we record every single extent we allocate in a preallocation, there's no way we can return the file to it's previous state. We could be allocating thousands of extents in a single syscall. Hence rollback on failure is pretty much doomed on all existing filesystems, so it's not required. > However, what I see is a different behavior for different filesystems, for > instance, if the file already has some blocks allocated, Ext4 will leave the > file with a partial pre-allocation made by fallocate, So will XFS. You just need to fragment freespace or preallocate over a sparse range with some blocks allocated so that the ENOSPC occurs on the second+ extent that is allocated in the range given. > while XFS does not change > file size of add any extra blocks to the file at all. Right, XFS will not change the file size unless the preallocation operation completes successfully. > If the original file size is 0, it changes a bit, Ext4 will still change the > file size and leave the partially allocated blocks there, while XFS won't change > the file size, but will keep the partially pre-allocated blocks. I think ext4 shouldn't be changing the file size in this case. Write a fstest to trigger this enospc behaviour and have it fail if the file size changes on a preallocation that returns ENOSPC.... > I wonder how it should really behave or if it is a filesystem decision? Should be consistent across all filesystems, hence the fstest... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
