how to verify the result of systemtap

[Humagillani]

hi , im using this command /scsi_fault_injection_test_tool-1.0.1/r_timeout.stp 8 17 33 1 12 -g -I /scsi_fault_injection_test_tool-1.0.0/fault_injection_common_sata -v

and successfully get the Pass 5: starting run. but how can i get the results, and from where, because when i cat /dev/md127 it give me nothing .

and how can i run the systemtap script print ?

[dwalkes]

but how can i get the results, and from where, because when i cat /dev/md127 it give me nothing .

Since you are running the read timeout script with 1=inode in the inode/lba argument, you should see a read timeout if you attempt to access inode 12 on device with major number 8, minor number between 17 and 33 inclusive. What cat /dev/md127 will do will depend on 1) whether the device is in the range of major number 8, minor number between 17 and 33 and 2) where inode 12 is located on disk. I don't know that you will see an error or debug log from the script, I can't remember whether this is the case (it's been several years since I tried it) but you will probably see errors in the system log from the read command timing out. Typically I've used these scripts to simulate errors in areas of the disk other software I wrote was reading and verify the error handling in my software. So in the case you gave, this would be appropriate if you know the software you are testing accessing inode 12 on the specified device.

To simplify for starters you might just want to pick LBA instead of inode by setting and use LBA 0, by setting the 4th and 5th argument to 0, then use the dd command to read LBA 0 of the device with something like: dd if=/dev/xxx skip=0 bs=512 count=1 Where /dev/xxx is the device you've selected with the major/minor range options

Hope this helps.

[Humagillani]

i ever tried it with sector_rerr.stp but still im unable to get results,