1 BLOCK DEVICE VERIFICATION TOOL. ( bdevt )
2 ==========================================
5 To build this tool you just need to invoke make at command prompt.
8 this will compile the sources and build bdevt in this directory.
13 ./bdevt [OPTION]... <device-name> ...
16 -t {seconds} for --timestamp, set test time (default=current time())
17 -o {offset} for --offset, offset in kB of start of test (default=0)
18 -r run test in read (verify) mode
19 -w run test in write (test-pattern) mode (default=r&w)
21 -p for --partial, for partial check (1GB steps)
22 -l for --long, full check (default 4k)
23 -c for --chunksize, IO chunk size (default=1048576)
24 -f for --force, force test to run without confirmation
25 --help to display help.
27 Guide lines for using this tool:
28 It is expected that bdevt tool will be run on large size devices (TB),
29 So it is always better to run bdevt tool in verbose mode, So that one can easily
30 restart device testing from the point at which it had stoped.
33 [root@tucker bdevt]# ./bdevt -v -f -w --timestamp=1009839028 /dev/hda5
34 Number of sectors: 49158837, this makes 23.441 GB
36 Current write offset: 5078016 kB
38 If due to some reason sombody breaks execution at this point then one can
39 easily restart device from the same point by picking the same offset
40 displayed in by verbose as explained below.
42 [root@tucker bdevt]# ./bdevt -v -f -w --offset=5078016 --timestamp=1009839028 /dev/hda5
43 Number of sectors: 49158837, this makes 23.441 GB
45 Current write offset: 9726208 kB
47 One can use similar things for read only and read write modes also.