diff options
| author | Josef Bacik <jbacik@fusionio.com> | 2013-03-28 13:51:03 -0400 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2013-04-23 18:56:26 +0200 |
| commit | 580ccf9e2ef4607f5b67b531190e7842c4b2b0db (patch) | |
| tree | 7b492bfe8f9c42934f3cc592a5a25897bb1c977d /volumes.c | |
| parent | 82ecc3670856efc9e9faa62bab75dd216ec2be94 (diff) | |
Btrfs-progs: add csum tree checks to btrfsck
Looking at a recent user problem I noticed there are weird cases we could
possibly be leaving csums in place for an extent we've free'd. I don't think
this can happen unless the extent tree is also corrupt, but just in case I'm
adding sanity checks to btrfsck. This way we will catch this if it happens
normally since xfstests runs btrfsck between each run. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Diffstat (limited to 'volumes.c')
0 files changed, 0 insertions, 0 deletions