Re: [PATCH 1/3] btrfs: improve inode's outstanding_extents computation

2017-01-22 Thread Qu Wenruo
Hi Liu, Sorry for the late reply. At 01/04/2017 07:36 AM, Liu Bo wrote: (Resend this reply due to a message that there is an invalid email address.) On Tue, Jan 03, 2017 at 01:00:45PM -0800, Liu Bo wrote: On Fri, Nov 11, 2016 at 04:39:45PM +0800, Wang Xiaoguang wrote: This issue was

Re: [PATCH 1/3] btrfs: improve inode's outstanding_extents computation

2017-01-03 Thread Liu Bo
(Resend this reply due to a message that there is an invalid email address.) On Tue, Jan 03, 2017 at 01:00:45PM -0800, Liu Bo wrote: > On Fri, Nov 11, 2016 at 04:39:45PM +0800, Wang Xiaoguang wrote: > > This issue was revealed by modifying BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, > > When modifying

Re: [PATCH 1/3] btrfs: improve inode's outstanding_extents computation

2017-01-03 Thread Liu Bo
On Fri, Nov 11, 2016 at 04:39:45PM +0800, Wang Xiaoguang wrote: > This issue was revealed by modifying BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, > When modifying BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often > gets these warnings from btrfs_destroy_inode(): >

[PATCH 1/3] btrfs: improve inode's outstanding_extents computation

2016-11-11 Thread Wang Xiaoguang
This issue was revealed by modifying BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, When modifying BTRFS_MAX_EXTENT_SIZE(128MB) to 64KB, fsstress test often gets these warnings from btrfs_destroy_inode(): WARN_ON(BTRFS_I(inode)->outstanding_extents);