qa/.../osd-scrub-test.sh: don't use /etc/fstab to corrupt the data

Generally, it's more portable not to rely on specific system files to be
readable.  Specifically, container environments may not have an fstab.
Instead, just generate another random file.

Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit d8be43e39ad532a15db143c93e78029f075e3658)

diff --git a/qa/standalone/scrub/osd-scrub-test.sh b/qa/standalone/scrub/osd-scrub-test.sh
index 3393c34e789520258b2077fba6c4231932c382d2..118309a2cc74cecda1825f78e27643176135a47f 100755 (executable)
--- a/qa/standalone/scrub/osd-scrub-test.sh
+++ b/qa/standalone/scrub/osd-scrub-test.sh
@@ -74,7 +74,10 @@ function TEST_scrub_test() {
       local anotherosd="2"
     fi
 
-    objectstore_tool $dir $anotherosd obj1 set-bytes /etc/fstab
+    CORRUPT_DATA="corrupt-data.$$"
+    dd if=/dev/urandom of=$CORRUPT_DATA bs=512 count=1
+    objectstore_tool $dir $anotherosd obj1 set-bytes $CORRUPT_DATA
+    rm -f $CORRUPT_DATA
 
     local pgid="${poolid}.0"
     pg_deep_scrub "$pgid" || return 1