On Thu, Mar 22, 2018 at 08:12:31AM +0800, Qu Wenruo wrote:
> > Applied, thanks. I had to fix the test, fallocate may fail, so a file of
> > given size is created directly.
>
> The fix looks good, and I learn a new trick.
>
> But I'm wondering how could it fail.
>
> Nowadays /tmp should be tmpfs
On 2018年03月21日 23:51, David Sterba wrote:
> On Tue, Mar 20, 2018 at 02:42:23PM +0800, Qu Wenruo wrote:
>> The patch is based on v4.15.1, and is designed to replace the old patch
>> in devel branch.
>>
>> Kernel doesn't support dropping range inside inline extent, and prevents
>> such thing happen
On Tue, Mar 20, 2018 at 02:42:23PM +0800, Qu Wenruo wrote:
> The patch is based on v4.15.1, and is designed to replace the old patch
> in devel branch.
>
> Kernel doesn't support dropping range inside inline extent, and prevents
> such thing happening by limiting max inline extent size to
> min(ma
The patch is based on v4.15.1, and is designed to replace the old patch
in devel branch.
Kernel doesn't support dropping range inside inline extent, and prevents
such thing happening by limiting max inline extent size to
min(max_inline, sectorsize - 1) in cow_file_range_inline().
However btrfs-pr
