Apparently with newer btrfs-progs (seen with 4.4) 100M are not enough
for a btrfs filesystem; hence double the size of the partitions
created in the test of btrfs_image, so now 200M are enough for btrfs.
---
generator/actions.ml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/generator/actions.ml b/generator/actions.ml
index 75d3fc5..9ea5736 100644
--- a/generator/actions.ml
+++ b/generator/actions.ml
@@ -12680,8 +12680,8 @@ This enable skinny metadata extent refs." };
tests = [
InitEmpty, Always, TestRun (
[["part_init"; "/dev/sda"; "mbr"];
- ["part_add"; "/dev/sda"; "p"; "64";
"204799"];
- ["part_add"; "/dev/sda"; "p"; "204800";
"409599"];
+ ["part_add"; "/dev/sda"; "p"; "64";
"409599"];
+ ["part_add"; "/dev/sda"; "p"; "409600";
"819199"];
["mkfs_btrfs"; "/dev/sda1"; ""; "";
"NOARG"; ""; "NOARG"; "NOARG"; "";
""];
["mkfs_btrfs"; "/dev/sda2"; ""; "";
"NOARG"; ""; "NOARG"; "NOARG"; "";
""];
["mount"; "/dev/sda1"; "/"];
--
2.5.0