Bug #36604
Updated by David Zafman over 5 years ago
I ran this in my build tree as follows: <pre> cd build ../qa/run-standalone.sh osd-bluefs-volume-ops.sh ... ../qa/standalone/osd/osd-bluefs-volume-ops.sh:87: TEST_bluestore: kill 67496 ../qa/standalone/osd/osd-bluefs-volume-ops.sh:87: TEST_bluestore: sleep 1 ../qa/standalone/osd/osd-bluefs-volume-ops.sh:87: TEST_bluestore: kill 67496 ../qa/standalone/osd/osd-bluefs-volume-ops.sh:87: TEST_bluestore: sleep 1 ../qa/standalone/osd/osd-bluefs-volume-ops.sh:87: TEST_bluestore: kill 67496 ../qa/standalone/osd/osd-bluefs-volume-ops.sh: line 87: kill: (67496) - No such process ../qa/standalone/osd/osd-bluefs-volume-ops.sh:88: TEST_bluestore: ceph osd down 3 *** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH *** marked down osd.3. ../qa/standalone/osd/osd-bluefs-volume-ops.sh:91: TEST_bluestore: ceph-objectstore-tool --type bluestore --data-path td/osd-bluefs-volume-ops/0 --op fsck --no-mon-config +--no-mon-config+ fsck found no errors ../qa/standalone/osd/osd-bluefs-volume-ops.sh:94: TEST_bluestore: ceph-bluestore-tool --path td/osd-bluefs-volume-ops/0 bluefs-bdev-sizes inferring bluefs devices from bluestore path HANG </pre> I sent a termination to the ceph-bluestore-tool command. I see a ceph-mon so I don't know why the previous command used +--no-mon-connfig+ <pre> ../qa/standalone/osd/osd-bluefs-volume-ops.sh: line 52: 68109 Terminated ceph-bluestore-tool --path $dir/0 bluefs-bdev-sizes ../qa/standalone/osd/osd-bluefs-volume-ops.sh:96: TEST_bluestore: ceph-bluestore-tool --path td/osd-bluefs-volume-ops/0 --devs-source td/osd-bluefs-volume-ops/0/block.wal --dev-target td/osd-bluefs-volume-ops/0/block.db --command bluefs-bdev-migrate too many positional options have been specified on the command line </pre> The line 96 command also seems is failing after I terminate the hung command on line 94.