Searched refs:blkverify (Results 1 – 14 of 14) sorted by relevance
/openbmc/qemu/docs/devel/testing/ |
H A D | blkverify.rst | 1 Block driver correctness testing with ``blkverify`` 7 This document describes how to use the ``blkverify`` protocol to test that a block 16 ``blkverify`` solves this problem by catching data corruption inside QEMU the first 22 The ``blkverify`` protocol has two child block devices, the "test" device and the 31 After a mirrored read operation completes, ``blkverify`` will compare the data and 60 This error is caught by ``blkverify``:: 62 $ ./qemu-io -c 'read 0 512' blkverify:a.img:b.img 63 blkverify: read sector_num=0 nb_sectors=4 contents mismatch in sector 0 70 -drive file=blkverify:raw.img:test.qcow2 72 If the installation is aborted when ``blkverify`` detects corruption, use ``qemu-io``
|
H A D | index.rst | 18 blkverify
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 099.out | 5 === Testing simple filename for blkverify === 7 blkverify:TEST_DIR/t.IMGFMT.compare:TEST_DIR/t.IMGFMT 9 === Testing filename reconstruction for blkverify === 11 blkverify:TEST_DIR/t.IMGFMT.compare:TEST_DIR/t.IMGFMT 19 …"driver": "blkdebug", "inject-error.0.event": "l1_update"}}, "driver": "blkverify", "raw": {"drive…
|
H A D | 071.out | 3 === Testing blkverify through filename === 15 blkverify: read offset=0 bytes=512 contents mismatch at offset 0 17 === Testing blkverify through file blockref === 29 blkverify: read offset=0 bytes=512 contents mismatch at offset 0 52 === Testing blkverify on existing block device === 59 blkverify: read offset=0 bytes=512 contents mismatch at offset 0 62 === Testing blkverify on existing raw block device === 69 blkverify: read offset=0 bytes=512 contents mismatch at offset 0
|
H A D | 081.out | 86 == checking the blkverify mode with broken content == 95 == checking the blkverify mode with valid content == 99 == checking the blkverify mode with invalid settings == 100 qemu-io: can't open: blkverify=on can only be set if there are exactly two files and vote-threshold… 117 {"error": {"class": "GenericError", "desc": "Cannot add a child to a quorum in blkverify mode"}} 142 {"error": {"class": "GenericError", "desc": "blkverify=on can only be set if there are exactly two …
|
H A D | 139 | 186 def addBlkVerify(self, blkverify, test, raw): argument 189 self.checkBlockDriverState(blkverify, False) 200 'node-name': blkverify, 206 self.checkBlockDriverState(blkverify)
|
H A D | 099 | 49 _require_drivers blkdebug blkverify
|
H A D | 071 | 42 _require_drivers blkdebug blkverify
|
/openbmc/qemu/block/ |
H A D | meson.build | 9 'blkverify.c',
|
/openbmc/qemu/qapi/ |
H A D | block-core.json | 3201 'data': [ 'blkdebug', 'blklogwrites', 'blkreplay', 'blkverify', 'bochs', 3909 # Driver specific block device options for blkverify. 3951 # @blkverify: true if the driver must print content mismatch set to 3967 'data': { '*blkverify': 'bool', 4716 'blkverify': 'BlockdevOptionsBlkverify',
|
/openbmc/qemu/ |
H A D | MAINTAINERS | 3935 blkverify 3939 F: block/blkverify.c 3940 F: docs/devel/blkverify.rst
|
/openbmc/ |
D | opengrok1.0.log | [all...] |
D | opengrok2.0.log | [all...] |
/openbmc/linux/ |
H A D | opengrok0.0.log | [all...] |