diff options
| author | Josef Bacik <jbacik@fb.com> | 2015-02-06 13:03:12 -0500 |
|---|---|---|
| committer | Josef Bacik <jbacik@fb.com> | 2015-02-09 14:53:15 -0500 |
| commit | 797a937e5dd8db0092add633a80f3cd698e182df (patch) | |
| tree | 8b2b49b5b4ecee6632f5fb92207979db10627590 /btrfs-image.c | |
| parent | c7e3b63b7e231ed1d9a47ca735a7ead112b47078 (diff) | |
Btrfs-progs: Introduce metadump_v2
The METADUMP super flag makes us skip doing the chunk tree reading which isn't
helpful for the new restore since we have a valid chunk tree. But we still want
to have a way for the kernel to know that this is a metadump restore so it
doesn't do things like verify data checksums. We also want to skip some of the
device extent checks in fsck since those will obviously not match. Thanks,
Signed-off-by: Josef Bacik <jbacik@fb.com>
Diffstat (limited to 'btrfs-image.c')
| -rw-r--r-- | btrfs-image.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/btrfs-image.c b/btrfs-image.c index ea855425..feb4a620 100644 --- a/btrfs-image.c +++ b/btrfs-image.c @@ -1455,6 +1455,7 @@ static int update_super(struct mdrestore_struct *mdres, u8 *buffer) struct btrfs_chunk *chunk; struct btrfs_disk_key *disk_key; struct btrfs_key key; + u64 flags = btrfs_super_flags(super); u32 new_array_size = 0; u32 array_size; u32 cur = 0; @@ -1510,6 +1511,8 @@ static int update_super(struct mdrestore_struct *mdres, u8 *buffer) if (mdres->clear_space_cache) btrfs_set_super_cache_generation(super, 0); + flags |= BTRFS_SUPER_FLAG_METADUMP_V2; + btrfs_set_super_flags(super, flags); btrfs_set_super_sys_array_size(super, new_array_size); csum_block(buffer, BTRFS_SUPER_INFO_SIZE); |