sysfs-block 1.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
  1. What: /sys/block/<disk>/stat
  2. Date: February 2008
  3. Contact: Jerome Marchand <jmarchan@redhat.com>
  4. Description:
  5. The /sys/block/<disk>/stat files displays the I/O
  6. statistics of disk <disk>. They contain 11 fields:
  7. 1 - reads completed succesfully
  8. 2 - reads merged
  9. 3 - sectors read
  10. 4 - time spent reading (ms)
  11. 5 - writes completed
  12. 6 - writes merged
  13. 7 - sectors written
  14. 8 - time spent writing (ms)
  15. 9 - I/Os currently in progress
  16. 10 - time spent doing I/Os (ms)
  17. 11 - weighted time spent doing I/Os (ms)
  18. For more details refer Documentation/iostats.txt
  19. What: /sys/block/<disk>/<part>/stat
  20. Date: February 2008
  21. Contact: Jerome Marchand <jmarchan@redhat.com>
  22. Description:
  23. The /sys/block/<disk>/<part>/stat files display the
  24. I/O statistics of partition <part>. The format is the
  25. same as the above-written /sys/block/<disk>/stat
  26. format.
  27. What: /sys/block/<disk>/integrity/format
  28. Date: June 2008
  29. Contact: Martin K. Petersen <martin.petersen@oracle.com>
  30. Description:
  31. Metadata format for integrity capable block device.
  32. E.g. T10-DIF-TYPE1-CRC.
  33. What: /sys/block/<disk>/integrity/read_verify
  34. Date: June 2008
  35. Contact: Martin K. Petersen <martin.petersen@oracle.com>
  36. Description:
  37. Indicates whether the block layer should verify the
  38. integrity of read requests serviced by devices that
  39. support sending integrity metadata.
  40. What: /sys/block/<disk>/integrity/tag_size
  41. Date: June 2008
  42. Contact: Martin K. Petersen <martin.petersen@oracle.com>
  43. Description:
  44. Number of bytes of integrity tag space available per
  45. 512 bytes of data.
  46. What: /sys/block/<disk>/integrity/write_generate
  47. Date: June 2008
  48. Contact: Martin K. Petersen <martin.petersen@oracle.com>
  49. Description:
  50. Indicates whether the block layer should automatically
  51. generate checksums for write requests bound for
  52. devices that support receiving integrity metadata.