aboutsummaryrefslogtreecommitdiffstats
path: root/utils.h
diff options
context:
space:
mode:
authorSam Tygier <samtygier@yahoo.co.uk>2015-05-30 15:54:48 +0100
committerDavid Sterba <dsterba@suse.cz>2015-06-02 17:02:19 +0200
commitfbb356632c19c9262231e2062d2f708574f794ad (patch)
tree600f4608c547983d27a9223d2992384cf9b2814a /utils.h
parent1e9a6b698479ad759270270d585a5af36253cc30 (diff)
downloadbtrfs-progs-fbb356632c19c9262231e2062d2f708574f794ad.tar.gz
btrfs-progs-fbb356632c19c9262231e2062d2f708574f794ad.tar.xz
btrfs-progs-fbb356632c19c9262231e2062d2f708574f794ad.zip
btrfs-progs: mkfs: check metadata redundancy
Currently BTRFS allows you to make bad choices of data and metadata levels. For example -d raid1 -m raid0 means you can only use half your total disk space, but will lose everything if 1 disk fails. It should give a warning in these cases. When making a filesystem, check that metadata mode is at least as redundant as the data mode. For example give warning when: -d raid1 -m raid0 Signed-off-by: Sam Tygier <samtygier@yahoo.co.uk> [make the check more visible in mkfs output] Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'utils.h')
-rw-r--r--utils.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/utils.h b/utils.h
index 5657c74..a0057de 100644
--- a/utils.h
+++ b/utils.h
@@ -144,6 +144,7 @@ int test_dev_for_mkfs(char *file, int force_overwrite, char *estr);
int get_label_mounted(const char *mount_path, char *labelp);
int test_num_disk_vs_raid(u64 metadata_profile, u64 data_profile,
u64 dev_cnt, int mixed, char *estr);
+int group_profile_max_safe_loss(u64 flags);
int is_vol_small(char *file);
int csum_tree_block(struct btrfs_root *root, struct extent_buffer *buf,
int verify);