summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAlan D. Brunelle <Alan.Brunelle@hp.com>2006-01-26 16:03:12 +0100
committerJens Axboe <axboe@suse.de>2006-01-26 16:03:12 +0100
commitf17c879dcf9c34d42cddfc5e9c4275fe08a90475 (patch)
tree1cbd73c31a398754a1df98c007afd6805f78b775 /README
parent7126171a8c687c5f455887939bdaa37436893d61 (diff)
downloadblktrace-f17c879dcf9c34d42cddfc5e9c4275fe08a90475.tar.gz
blktrace-f17c879dcf9c34d42cddfc5e9c4275fe08a90475.tar.bz2
[PATCH] Added blkrawverify utility
Diffstat (limited to 'README')
-rw-r--r--README9
1 files changed, 8 insertions, 1 deletions
diff --git a/README b/README
index b71dae0..5f79e36 100644
--- a/README
+++ b/README
@@ -126,6 +126,14 @@ $ verify_blkparse filename
the events in the file are correctly time ordered. If an entry
is found that isn't ordered, it's dumped to stdout.
+$ blkrawverify <dev> [<dev>...]
+
+ The blkrawverify utility can be used to verify data retrieved
+ via blktrace. It will check for valid event formats, forward
+ progressing sequence numbers and time stamps, also does reasonable
+ checks for other potential issues within invidividual events.
+
+ Errors found will be tracked in <dev>.verify.out.
If you want to do live tracing, you can pipe the data between blktrace
and blkparse:
@@ -142,7 +150,6 @@ the network with eg netcat:
Which will send the traces from tracehost to parsehost over the network on
the defined port number.
-
Documentation
-------------