On Feb 13 2023, Qu Wenruo wrote:
> On 2023/2/13 00:20, Andreas Schwab wrote:
>> When I print ce->size in __btrfs_map_block, it is almost always
>> 1073741824, which looks bogus.
>>
> Can you provide the image of that filesystem?
How do I do that?
--
Andreas Schwab, sch...@linux-m68k.org
GPG
On 2023/2/13 00:20, Andreas Schwab wrote:
When I print ce->size in __btrfs_map_block, it is almost always
1073741824, which looks bogus.
Can you provide the image of that filesystem?
Thanks,
Qu
When I print ce->size in __btrfs_map_block, it is almost always
1073741824, which looks bogus.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
The length returned by btrfs_map_block is clearly bogus:
read_extent_data: cur=615817216, orig_len=16384, cur_len=16384
read_extent_data: btrfs_map_block: cur_len=479944704; ret=0
read_extent_data: ret=0
read_extent_data: cur=615833600, orig_len=4096, cur_len=4096
read_extent_data:
On Dez 30 2022, Qu Wenruo wrote:
> [BUG]
> Since btrfs supports single device RAID0 at mkfs time after btrfs-progs
> v5.14, if we create a single device raid0 btrfs, and created a file
> crossing stripe boundary:
>
> # mkfs.btrfs -m dup -d raid0 test.img
> # mount test.img mnt
> # xfs_io -f
On Fri, Dec 30, 2022 at 09:07:05AM +0800, Qu Wenruo wrote:
> [BUG]
> Since btrfs supports single device RAID0 at mkfs time after btrfs-progs
> v5.14, if we create a single device raid0 btrfs, and created a file
> crossing stripe boundary:
>
> # mkfs.btrfs -m dup -d raid0 test.img
> # mount
[BUG]
Since btrfs supports single device RAID0 at mkfs time after btrfs-progs
v5.14, if we create a single device raid0 btrfs, and created a file
crossing stripe boundary:
# mkfs.btrfs -m dup -d raid0 test.img
# mount test.img mnt
# xfs_io -f -c "pwrite 0 128K" mnt/file
# umount mnt
7 matches
Mail list logo