At 06/21/2017 08:10 PM, Adam Borowski wrote:
On Wed, Jun 21, 2017 at 05:28:50PM +0800, Qu Wenruo wrote:
Would you please try this patch based on v4.12-rc5 and try to reproduce
the kernel warning?
It would be better to eliminate the noisy by ensure there is no other fiemap
caller on btrfs.
Here's my current dmesg buffer from a single dpkg --reinstall invocation.
Thanks for the dmesg!
The problem is if the fiemap range is smaller than the extent, we will
exit without emit fiemap extent to VFS, leaving it cached.
As shown in your dmesg:
---
extent_fiemap: enter: root=10152 inode=5353157 start=0 len=4096
emit_fiemap_extent: entered: offset=0 phys=2012381351936 len=131072
flags=0x2008
emit_fiemap_extent: assigning new fiemap
emit_fiemap_extent: last exit ret=0
------------[ cut here ]------------
---
Your dmesg really helps a lot!
I'll send the fix in this week.
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
