btrfs: fix devs_max constraints for raid1c3 and raid1c4
authorDavid Sterba <dsterba@suse.com>
Wed, 27 Nov 2019 15:10:54 +0000 (16:10 +0100)
committerDavid Sterba <dsterba@suse.com>
Fri, 13 Dec 2019 13:09:23 +0000 (14:09 +0100)
commitcf93e15eca0bcb457b6a85b3480c1e379407dd26
tree17c72be0e3dd750087a6b9e03843e3b61956d191
parent994bf9cd78aa382c0c3c70b7cf9c00f7529176c2
btrfs: fix devs_max constraints for raid1c3 and raid1c4

The value 0 for devs_max means to spread the allocated chunks over all
available devices, eg. stripe for RAID0 or RAID5. This got mistakenly
copied to the RAID1C3/4 profiles. The intention is to have exactly 3 and
4 copies respectively.

Fixes: 47e6f7423b91 ("btrfs: add support for 3-copy replication (raid1c3)")
Fixes: 8d6fac0087e5 ("btrfs: add support for 4-copy replication (raid1c4)")
Signed-off-by: David Sterba <dsterba@suse.com>
fs/btrfs/volumes.c