109
109
Description:
110
110
Indicates whether a storage device is capable of storing
111
111
integrity metadata. Set if the device is T10 PI-capable.
112
+ This flag is set to 1 if the storage media is formatted
113
+ with T10 Protection Information. If the storage media is
114
+ not formatted with T10 Protection Information, this flag
115
+ is set to 0.
112
116
113
117
114
118
What: /sys/block/<disk>/integrity/format
117
121
Description:
118
122
Metadata format for integrity capable block device.
119
123
E.g. T10-DIF-TYPE1-CRC.
124
+ This field describes the type of T10 Protection Information
125
+ that the block device can send and receive.
126
+ If the device can store application integrity metadata but
127
+ no T10 Protection Information profile is used, this field
128
+ contains "nop".
129
+ If the device does not support integrity metadata, this
130
+ field contains "none".
120
131
121
132
122
133
What: /sys/block/<disk>/integrity/protection_interval_bytes
@@ -142,7 +153,17 @@ Date: June 2008
142
153
Contact: Martin K. Petersen <
[email protected] >
143
154
Description:
144
155
Number of bytes of integrity tag space available per
145
- 512 bytes of data.
156
+ protection_interval_bytes, which is typically
157
+ the device's logical block size.
158
+ This field describes the size of the application tag
159
+ if the storage device is formatted with T10 Protection
160
+ Information and permits use of the application tag.
161
+ The tag_size is reported in bytes and indicates the
162
+ space available for adding an opaque tag to each block
163
+ (protection_interval_bytes).
164
+ If the device does not support T10 Protection Information
165
+ (even if the device provides application integrity
166
+ metadata space), this field is set to 0.
146
167
147
168
148
169
What: /sys/block/<disk>/integrity/write_generate
0 commit comments