read partially
* file is read but is corrupted
* (any) metadata being corrupted or not read at all, etc
The easiest way to reproduce this is to read a large enough file that
its EXTENT_DATA items don't fit into a single leaf.
Signed-off-by: Yevgeny Popovych
Cc: Marek Behun
---
fs/btrfs/c
-CHUNK_ITEM, which makes
only some portion of CHUNK_ITEMs being read.
Change it to skip over non-chunk items.
Signed-off-by: Yevgeny Popovych
Cc: Marek Behun
Cc: Sergey Struzh
---
fs/btrfs/chunk-map.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/chunk-map.c b/fs/btrfs
of empty super_roots.
* btrfs_read_superblock() verifies number of devices from the superblock
itself, not newest root_backup.
Signed-off-by: Yevgeny Popovych
Cc: Marek Behun
Cc: Sergey Struzh
---
fs/btrfs/btrfs.h | 1 -
fs/btrfs/super.c | 30 ++
2 files changed
Just a kindly reminder :)
On 09/07/2018 12:59 PM, Yevgeny Popovych wrote:
> When traversing slots in a btree (via btrfs_path) with btrfs_next_slot(),
> we didn't correctly identify that the last slot in the leaf was reached
> and we should jump to the next leaf.
>
> This co
x reading large files? I haven't
> encountered such an error yet, but can try creating a large enough
> file. How large should it be?
>
> On Mon, 1 Oct 2018 08:50:11 +0300
> Yevgeny Popovych wrote:
>
>> Just a kindly reminder :)
>>
>> On 09/07/2018 12:59
5 matches
Mail list logo