diff options
| author | Sam Tygier <samtygier@yahoo.co.uk> | 2015-05-30 15:54:48 +0100 |
|---|---|---|
| committer | David Sterba <dsterba@suse.cz> | 2015-06-02 17:02:19 +0200 |
| commit | fbb356632c19c9262231e2062d2f708574f794ad (patch) | |
| tree | 600f4608c547983d27a9223d2992384cf9b2814a /utils.c | |
| parent | 1e9a6b698479ad759270270d585a5af36253cc30 (diff) | |
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.c')
| -rw-r--r-- | utils.c | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -2354,6 +2354,24 @@ int test_num_disk_vs_raid(u64 metadata_profile, u64 data_profile, return 0; } +int group_profile_max_safe_loss(u64 flags) +{ + switch (flags & BTRFS_BLOCK_GROUP_PROFILE_MASK) { + case 0: /* single */ + case BTRFS_BLOCK_GROUP_DUP: + case BTRFS_BLOCK_GROUP_RAID0: + return 0; + case BTRFS_BLOCK_GROUP_RAID1: + case BTRFS_BLOCK_GROUP_RAID5: + case BTRFS_BLOCK_GROUP_RAID10: + return 1; + case BTRFS_BLOCK_GROUP_RAID6: + return 2; + default: + return -1; + } +} + /* Check if disk is suitable for btrfs * returns: * 1: something is wrong, estr provides the error |