On Mon, May 23, 2016 at 7:05 AM, Wang Xiaoguang
wrote:
> hello,
>
>
> On 05/19/2016 07:01 PM, Filipe Manana wrote:
>>
>> On Thu, May 19, 2016 at 11:49 AM, Wang Xiaoguang
>> wrote:
>>>
>>> This issue was revealed by modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB,
>>> When modifing BTRFS_MAX_EXTENT_
hello,
On 05/19/2016 07:01 PM, Filipe Manana wrote:
On Thu, May 19, 2016 at 11:49 AM, Wang Xiaoguang
wrote:
This issue was revealed by modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB,
When modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often gets
these warnings from btrfs_destroy_i
On Thu, May 19, 2016 at 11:49 AM, Wang Xiaoguang
wrote:
> This issue was revealed by modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB,
> When modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often gets
> these warnings from btrfs_destroy_inode():
> WARN_ON(BTRFS_I(inode)->outstand
This issue was revealed by modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB,
When modifing BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often gets
these warnings from btrfs_destroy_inode():
WARN_ON(BTRFS_I(inode)->outstanding_extents);
WARN_ON(BTRFS_I(inode)->reserved_extents);
