ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d16c5b49dd
Spdk/test/blobstore/btest.out.match

91 lines
2.5 KiB
Plaintext
Raw Normal View History

test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
Starting SPDK v19.10.1 / DPDK 19.08.0 initialization...
[ DPDK EAL parameters: blobcli --no-shconf -c 0x1 --log-level=lib.eal:6 --log-level=lib.cryptodev:5 --log-level=user1:6 --iova-mode=pa --base-virtaddr=0x200000000000 --match-allocations --file-prefix=spdk_pid1641656 ]
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
SCRIPT NOW PROCESSING: -i
examples/blob_cli: Use spdk_bdev_create_bs_dev_ext() to pass bdev_name Update a few print outputs to out not product name but bdev name because bdev pointer is not available there after replacing spdk_bdev_get_by_name() and spdk_bdev_open() by spdk_bdev_open_ext(). Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Change-Id: I624fea3a0a12c1049e950bddae8cea9f88b16db5 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4702 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-10-14 15:19:44 +00:00
Init blobstore using bdev Name: Nvme0n1
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
blobstore init'd: ($(XX))
SCRIPT NOW PROCESSING: -l bdevs
List bdevs:
bdev Name: Nvme0n1
bdev Product Name: NVMe disk
SCRIPT NOW PROCESSING: -n 1
test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
New blob id $(N)
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
blob now has USED clusters of 1
SCRIPT NOW PROCESSING: -p $B0
Super Blob ID has been set.
SCRIPT NOW PROCESSING: -n 1
test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
New blob id $(N)
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
blob now has USED clusters of 1
SCRIPT NOW PROCESSING: -m $B1 test.pattern
Working...............................................................................................................................................................................................................................................................
Blob import complete (from test.pattern).
SCRIPT NOW PROCESSING: -d $B1 test.pattern.blob
Working................................................................................................................................................................................................................................................................
File write complete (to test.pattern.blob).
SCRIPT NOW PROCESSING: -x $B1 key val
Xattr has been set.
SCRIPT NOW PROCESSING: -s bs
Blobstore Public Info:
Using bdev Product Name: NVMe disk
API Version: $(N)
test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
super blob ID: $(N)
blobcli: modify blobcli to use io unit size instead of page size Signed-off-by: Piotr Pelplinski <piotr.pelplinski@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I824735548d4aaadefd09c943889f885c35d326c0 Reviewed-on: https://review.gerrithub.io/425545 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-09-17 10:05:44 +00:00
page size: $(N)
io unit size: $(N)
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
cluster size: 1048576
# free clusters: $(N)
blobstore type:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Blobstore Private Info:
Metadata start (pages): $(N)
Metadata length (pages): $(N)
SCRIPT NOW PROCESSING: -s $B1
Blob Public Info:
test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
blob ID: $(N)
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
# of clusters: 1
# of bytes: 1048576
# of pages: 256
# of xattrs: 1
xattrs:
(0) Name:key
(0) Value:
examples/blob: skip '\0' when dump xattr's value In show_blob(), value_len of xattr contains terminator '\0', which is printed as '.' when calling spdk_log_dump(). For example, we set key/value pair as <key1,xattr value>, we get "xattr value." but not "xattr value" when showing blob info. Skip '\0' will fix this. And "data[BUFSIZE]" seems redundant here, remove it. Signed-off-by: Richael Zhuang <richael.zhuang@arm.com> Change-Id: I4e7c3276e51f14badf43b660b80b24ae85bb0900 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1745 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-04-08 01:56:10 +00:00
00000000 76 61 6c val
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
Blob Private Info:
state: CLEAN
open ref count: 1
SCRIPT NOW PROCESSING: -r $B1 key
Xattr has been removed.
SCRIPT NOW PROCESSING: -s bs
Blobstore Public Info:
Using bdev Product Name: NVMe disk
API Version: 3
test/blob: fix match tool with blobcli Empty line in ignore file caused all output from the match tool to be ignored. This made the test to always pass, regardless of changes made. Next patch in series will be fixing the match tool, meanwhile this patch focuses on making the blobstore test match and ignore files right. This patch adjusts match file in following ways: - keep EAL and crypto output up to date - use $(N) to match any blob id - adjust out of date xattr value print Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ia0a2312d9691487acbdd06dc08451232171cc46d Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/483705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-03 11:58:28 +00:00
super blob ID: $(N)
blobcli: modify blobcli to use io unit size instead of page size Signed-off-by: Piotr Pelplinski <piotr.pelplinski@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I824735548d4aaadefd09c943889f885c35d326c0 Reviewed-on: https://review.gerrithub.io/425545 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-09-17 10:05:44 +00:00
page size: $(N)
io unit size: $(N)
test: add 'match' util and use it with blobstore Will follow this up with a doc change but want to make sure we're all good with it first. This is meant to not only beef up blobstore testing but provide the 'match' utilitiy for all test cases where we are currently calling an executable and either counting only on a return code to determine success or failure or worse yet we're just running it and if it doesn't explode we assume its a pass. The 'match' util was borrowed from the PMDK folks after first adding the "ignore" feature upstream to make it easier to use in SPDK. It works like this: When the developer checks in a test they create and check in the output of the test with two different file extensions: .ignore: should include a string per line for output lines that we want to totally ignore typically because they're platform specific so the output could be different from machine to machine. In this case I'm ignoring all output lines with 'DPDK' or 'EAL' or '...' in them. The first few are obvious, the last is because the test tool will print a varrying number of these as progress indicators. .match: this is a copy of the output that the developer 'fixes' up by replacing platform specific output strings with replacable tokens as described in the 'match' help. This is where you'd want to match an entire line minus something like a CPU count or free block count or something. The 'ignore' feature was added simply so we wouldn't have to edit every single line of an output file that had DPDK or EAL in it. Then you modify the test script to save the output and smply run the match util providing the name of the match file and if it fails to match the actual output with the saved output that's been token'ized the script will error. The obvious advantage here is that now we can confirm all of the output from a test executable is as we expect. Change-Id: I701d36ee83d37b6193e16ed3171e114f814e5eb3 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/397027 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-01-29 22:33:02 +00:00
cluster size: 1048576
# free clusters: $(N)
blobstore type:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Blobstore Private Info:
Metadata start (pages): $(N)
Metadata length (pages): $(N)
SCRIPT NOW PROCESSING: -X
Reference in New Issue Copy Permalink