[LTP] [PATCH] syscalls/fallocate04: Fix on Btrfs

[Alexey Kodanev <alexey.kodanev@oracle.com>]

Hi,
On 08/29/2016 12:44 PM, Cyril Hrubis wrote:
> Hi!
>>>> The size of a file can double on Btrfs temporarily even when we write
>>>> into a preallocated space because of internal Btrfs caches, at least
>>>> that is what I've been told by Btrfs devs. The internal caches are then
>>>> freed after some time, or can be force freed by syncing the file, which
>>>> is what this patch does.
>> So if we have available free space x Mb,  we can't allocate more than x
>> / 2 Mb and it's not a bug?
> It's the other way around. We preallocate x Mb for the file, then write
> into the preallocated space. The file size, as reported by stat(), may
> end up > x MB after the write temporarily on Btrfs because of caching.
> And this is not a bug since the only guarantee we have is that we don't
> get ENOSPC when writing into preallocated file region. There is nothing
> that forbids allocating more space temporarily if there is plenty of it.

I understand that the size might be larger and we are allocating in 
chunks for
that reason. But here we have "cache" that equals the size of 
allocation...  it just looks suspicious.

It's true, it doesn't matter if we have plenty of space and if we are 
testing
writes that shouldn't return ENOSPC.


> Another interesting testcase would be doing the same on the LTP loopback
> device that would be filled up after the file has been preallocated.
> That would likely force different codepath in the FS since there would
> be no avaialable free space left...

On btrfs it will be hard to do, I mean filling free space :)

Best regards,
Alexey