Qu Wenruo b3621da146 btrfs-progs: check/original: Detect invalid extent generation ... Much like what we have done in lowmem mode, also detect and report invalid extent generation in original mode. Unlike lowmem mode, we have extent_record::generation, which is the higher number of generations in EXTENT_ITEM, EXTENT_DATA or tree block header, so there is no need to check generations in different locations. For repair, we still need to depend on --init-extent-tree, as directly modifying extent items can easily cause conflicts with delayed refs, thus it should be avoided. Reviewed-by: Su Yue <Damenly_Su@gmx.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>		2020-01-09 14:27:10 +01:00
..
common.h	btrfs-progs: check: move device_record to main.c	2019-10-14 17:27:41 +02:00
main.c	btrfs-progs: check/original: Detect invalid extent generation	2020-01-09 14:27:10 +01:00
mode-common.c	btrfs-progs: check/lowmem: Fix a false alert on uninitialized value	2019-11-22 19:09:51 +01:00
mode-common.h	btrfs-progs: check/original: Fix inode mode in subvolume trees	2019-11-18 19:21:07 +01:00
mode-lowmem.c	btrfs-progs: check/lowmem: Detect invalid EXTENT_ITEM and EXTENT_DATA generation	2020-01-09 14:27:10 +01:00
mode-lowmem.h	btrfs-progs: check/lowmem: Check and repair root generation	2019-09-04 16:06:50 +02:00
mode-original.h	btrfs-progs: check/original: Add check and repair for invalid inode generation	2019-11-18 19:21:07 +01:00
qgroup-verify.c	btrfs-progs: move qgroup-verify.[ch] to check/	2019-10-14 17:27:35 +02:00
qgroup-verify.h	btrfs-progs: move qgroup-verify.[ch] to check/	2019-10-14 17:27:35 +02:00