aboutsummaryrefslogtreecommitdiffstats
path: root/extent_io.h
diff options
context:
space:
mode:
authorJosef Bacik <jbacik@fusionio.com>2013-04-04 09:57:50 -0400
committerDavid Sterba <dsterba@suse.cz>2013-04-23 18:56:21 +0200
commitd93cad2677613b0a31315e428ead5339612a4b1c (patch)
treebc78b1d7300f611929b4978920ac10b66fe49ebd /extent_io.h
parentbee9403728ce017c0b9a8384a0bcb342b331688a (diff)
downloadbtrfs-progs-d93cad2677613b0a31315e428ead5339612a4b1c.tar.gz
btrfs-progs-d93cad2677613b0a31315e428ead5339612a4b1c.tar.xz
btrfs-progs-d93cad2677613b0a31315e428ead5339612a4b1c.zip
Btrfs-progs: add a free space cache checker to fsck V2
In trying to track down a weird tree log problem I wanted to make sure that the free space cache was actually valid, which we currently have no way of doing. So this patch adds a bunch of support for the free space cache code and then a checker to fsck. Basically we go through and if we can actually load the free space cache then we will walk the extent tree and verify that the free space cache exactly matches what is in the extent tree. Hopefully this will always be correct, the only time it wouldn't is if the extent tree is corrupt or we have some sort of awful bug in the free space cache. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'extent_io.h')
-rw-r--r--extent_io.h4
1 files changed, 4 insertions, 0 deletions
diff --git a/extent_io.h b/extent_io.h
index 492daf6..a0308a9 100644
--- a/extent_io.h
+++ b/extent_io.h
@@ -41,6 +41,8 @@
#define EXTENT_CSUM (1 << 9)
#define EXTENT_IOBITS (EXTENT_LOCKED | EXTENT_WRITEBACK)
+struct btrfs_fs_info;
+
struct extent_io_tree {
struct cache_tree state;
struct cache_tree cache;
@@ -122,4 +124,6 @@ void memset_extent_buffer(struct extent_buffer *eb, char c,
unsigned long start, unsigned long len);
int set_extent_buffer_dirty(struct extent_buffer *eb);
int clear_extent_buffer_dirty(struct extent_buffer *eb);
+int read_data_from_disk(struct btrfs_fs_info *info, void *buf, u64 offset,
+ u64 bytes, int mirror);
#endif