qa/standalone/bluefs: Fix CBT bluefs-bdev-expand

There was a problem when expansion of 'block' device crossed location
of bdev label copy. The extra label that did not exist before and now
exists was not initialized.
This makes test to fail.

Signed-off-by: Adam Kupczyk <akupczyk@ibm.com>
(cherry picked from commit ebd3d454d53d90992773eaf77180ee0c926c2c7f)

diff --git a/qa/standalone/osd/osd-bluefs-volume-ops.sh b/qa/standalone/osd/osd-bluefs-volume-ops.sh
index aedfbc9b5cbbec88e5417c9d690563223da5fcc3..f7424de8ce1309a1074c853cd29097c41f5e368d 100755 (executable)
--- a/qa/standalone/osd/osd-bluefs-volume-ops.sh
+++ b/qa/standalone/osd/osd-bluefs-volume-ops.sh
@@ -72,7 +72,7 @@ function TEST_bluestore() {
 
     truncate $dir/0/block -s 4294967296 # 4GB
     ceph-bluestore-tool --path $dir/0 bluefs-bdev-expand || return 1
-    truncate $dir/1/block -s 4311744512 # 4GB + 16MB
+    truncate $dir/1/block -s 11811160064 # 11GB to get bdev label at 10737418240
     ceph-bluestore-tool --path $dir/1 bluefs-bdev-expand || return 1
     truncate $dir/2/block -s 4295099392 # 4GB + 129KB
     ceph-bluestore-tool --path $dir/2 bluefs-bdev-expand || return 1