Re: [PATCH 1/2] btrfs-progs: convert: Fix a bug which fails to insert hole file extent

2016-06-02 Thread David Sterba
On Thu, Jun 02, 2016 at 03:22:49PM +0800, Qu Wenruo wrote: > When copying inode, if there is a file referring part of a hole range, > convert will fail. > > The problem is, when calculating real extent bytenr, it doesn't check if > the original extent is a hole. > > In case the orinal extent is a

[PATCH 1/2] btrfs-progs: convert: Fix a bug which fails to insert hole file extent

2016-06-02 Thread Qu Wenruo
When copying inode, if there is a file referring part of a hole range, convert will fail. The problem is, when calculating real extent bytenr, it doesn't check if the original extent is a hole. In case the orinal extent is a hole, we still calculate bytenr using file_pos - found_extent_file_pos,