48 lines · plain
1What: /sys/block/dm-<num>/dm/name2Date: January 20093KernelVersion: 2.6.294Contact: dm-devel@redhat.com5Description: Device-mapper device name.6 Read-only string containing mapped device name.7Users: util-linux, device-mapper udev rules8 9What: /sys/block/dm-<num>/dm/uuid10Date: January 200911KernelVersion: 2.6.2912Contact: dm-devel@redhat.com13Description: Device-mapper device UUID.14 Read-only string containing DM-UUID or empty string15 if DM-UUID is not set.16Users: util-linux, device-mapper udev rules17 18What: /sys/block/dm-<num>/dm/suspended19Date: June 200920KernelVersion: 2.6.3121Contact: dm-devel@redhat.com22Description: Device-mapper device suspend state.23 Contains the value 1 while the device is suspended.24 Otherwise it contains 0. Read-only attribute.25Users: util-linux, device-mapper udev rules26 27What: /sys/block/dm-<num>/dm/rq_based_seq_io_merge_deadline28Date: March 201529KernelVersion: 4.130Contact: dm-devel@redhat.com31Description: Allow control over how long a request that is a32 reasonable merge candidate can be queued on the request33 queue. The resolution of this deadline is in34 microseconds (ranging from 1 to 100000 usecs).35 Setting this attribute to 0 (the default) will disable36 request-based DM's merge heuristic and associated extra37 accounting. This attribute is not applicable to38 bio-based DM devices so it will only ever report 0 for39 them.40 41What: /sys/block/dm-<num>/dm/use_blk_mq42Date: March 201543KernelVersion: 4.144Contact: dm-devel@redhat.com45Description: Request-based Device-mapper blk-mq I/O path mode.46 Contains the value 1 if the device is using blk-mq.47 Otherwise it contains 0. Read-only attribute.48