1 .\"
2 .\" CDDL HEADER START
3 .\"
4 .\" The contents of this file are subject to the terms of the
5 .\" Common Development and Distribution License (the "License").
6 .\" You may not use this file except in compliance with the License.
7 .\"
8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9 .\" or https://opensource.org/licenses/CDDL-1.0.
10 .\" See the License for the specific language governing permissions
11 .\" and limitations under the License.
12 .\"
13 .\" When distributing Covered Code, include this CDDL HEADER in each
14 .\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15 .\" If applicable, add the following below this CDDL HEADER, with the
16 .\" fields enclosed by brackets "[]" replaced with your own identifying
17 .\" information: Portions Copyright [yyyy] [name of copyright owner]
18 .\"
19 .\" CDDL HEADER END
20 .\"
21 .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
22 .\" Copyright (c) 2012, 2018 by Delphix. All rights reserved.
23 .\" Copyright (c) 2012 Cyril Plisko. All Rights Reserved.
24 .\" Copyright (c) 2017 Datto Inc.
25 .\" Copyright (c) 2018 George Melikov. All Rights Reserved.
26 .\" Copyright 2017 Nexenta Systems, Inc.
27 .\" Copyright (c) 2017 Open-E, Inc. All Rights Reserved.
28 .\"
29 .Dd May 27, 2021
30 .Dt ZPOOL-EVENTS 8
31 .Os
32 .
33 .Sh NAME
34 .Nm zpool-events
35 .Nd list recent events generated by kernel
36 .Sh SYNOPSIS
37 .Nm zpool
38 .Cm events
39 .Op Fl vHf
40 .Op Ar pool
41 .Nm zpool
42 .Cm events
43 .Fl c
44 .
45 .Sh DESCRIPTION
46 Lists all recent events generated by the ZFS kernel modules.
47 These events are consumed by the
48 .Xr zed 8
49 and used to automate administrative tasks such as replacing a failed device
50 with a hot spare.
51 For more information about the subclasses and event payloads
52 that can be generated see
53 .Sx EVENTS
54 and the following sections.
55 .
56 .Sh OPTIONS
57 .Bl -tag -compact -width Ds
58 .It Fl c
59 Clear all previous events.
60 .It Fl f
61 Follow mode.
62 .It Fl H
63 Scripted mode.
64 Do not display headers, and separate fields by a
65 single tab instead of arbitrary space.
66 .It Fl v
67 Print the entire payload for each event.
68 .El
69 .
70 .Sh EVENTS
71 These are the different event subclasses.
72 The full event name would be
73 .Sy ereport.fs.zfs.\& Ns Em SUBCLASS ,
74 but only the last part is listed here.
75 .Pp
76 .Bl -tag -compact -width "vdev.bad_guid_sum"
77 .It Sy checksum
78 Issued when a checksum error has been detected.
79 .It Sy io
80 Issued when there is an I/O error in a vdev in the pool.
81 .It Sy data
82 Issued when there have been data errors in the pool.
83 .It Sy deadman
84 Issued when an I/O request is determined to be "hung", this can be caused
85 by lost completion events due to flaky hardware or drivers.
86 See
87 .Sy zfs_deadman_failmode
88 in
89 .Xr zfs 4
90 for additional information regarding "hung" I/O detection and configuration.
91 .It Sy delay
92 Issued when a completed I/O request exceeds the maximum allowed time
93 specified by the
94 .Sy zio_slow_io_ms
95 module parameter.
96 This can be an indicator of problems with the underlying storage device.
97 The number of delay events is ratelimited by the
98 .Sy zfs_slow_io_events_per_second
99 module parameter.
100 .It Sy config
101 Issued every time a vdev change have been done to the pool.
102 .It Sy zpool
103 Issued when a pool cannot be imported.
104 .It Sy zpool.destroy
105 Issued when a pool is destroyed.
106 .It Sy zpool.export
107 Issued when a pool is exported.
108 .It Sy zpool.import
109 Issued when a pool is imported.
110 .It Sy zpool.reguid
111 Issued when a REGUID (new unique identifier for the pool have been regenerated)
112 have been detected.
113 .It Sy vdev.unknown
114 Issued when the vdev is unknown.
115 Such as trying to clear device errors on a vdev that have failed/been kicked
116 from the system/pool and is no longer available.
117 .It Sy vdev.open_failed
118 Issued when a vdev could not be opened (because it didn't exist for example).
119 .It Sy vdev.corrupt_data
120 Issued when corrupt data have been detected on a vdev.
121 .It Sy vdev.no_replicas
122 Issued when there are no more replicas to sustain the pool.
123 This would lead to the pool being
124 .Em DEGRADED .
125 .It Sy vdev.bad_guid_sum
126 Issued when a missing device in the pool have been detected.
127 .It Sy vdev.too_small
128 Issued when the system (kernel) have removed a device, and ZFS
129 notices that the device isn't there any more.
130 This is usually followed by a
131 .Sy probe_failure
132 event.
133 .It Sy vdev.bad_label
134 Issued when the label is OK but invalid.
135 .It Sy vdev.bad_ashift
136 Issued when the ashift alignment requirement has increased.
137 .It Sy vdev.remove
138 Issued when a vdev is detached from a mirror (or a spare detached from a
139 vdev where it have been used to replace a failed drive - only works if
140 the original drive have been re-added).
141 .It Sy vdev.clear
142 Issued when clearing device errors in a pool.
143 Such as running
144 .Nm zpool Cm clear
145 on a device in the pool.
146 .It Sy vdev.check
147 Issued when a check to see if a given vdev could be opened is started.
148 .It Sy vdev.spare
149 Issued when a spare have kicked in to replace a failed device.
150 .It Sy vdev.autoexpand
151 Issued when a vdev can be automatically expanded.
152 .It Sy io_failure
153 Issued when there is an I/O failure in a vdev in the pool.
154 .It Sy probe_failure
155 Issued when a probe fails on a vdev.
156 This would occur if a vdev
157 have been kicked from the system outside of ZFS (such as the kernel
158 have removed the device).
159 .It Sy log_replay
160 Issued when the intent log cannot be replayed.
161 The can occur in the case of a missing or damaged log device.
162 .It Sy resilver.start
163 Issued when a resilver is started.
164 .It Sy resilver.finish
165 Issued when the running resilver have finished.
166 .It Sy scrub.start
167 Issued when a scrub is started on a pool.
168 .It Sy scrub.finish
169 Issued when a pool has finished scrubbing.
170 .It Sy scrub.abort
171 Issued when a scrub is aborted on a pool.
172 .It Sy scrub.resume
173 Issued when a scrub is resumed on a pool.
174 .It Sy scrub.paused
175 Issued when a scrub is paused on a pool.
176 .It Sy bootfs.vdev.attach
177 .El
178 .
179 .Sh PAYLOADS
180 This is the payload (data, information) that accompanies an
181 event.
182 .Pp
183 For
184 .Xr zed 8 ,
185 these are set to uppercase and prefixed with
186 .Sy ZEVENT_ .
187 .Pp
188 .Bl -tag -compact -width "vdev_cksum_errors"
189 .It Sy pool
190 Pool name.
191 .It Sy pool_failmode
192 Failmode -
193 .Sy wait ,
194 .Sy continue ,
195 or
196 .Sy panic .
197 See the
198 .Sy failmode
199 property in
200 .Xr zpoolprops 7
201 for more information.
202 .It Sy pool_guid
203 The GUID of the pool.
204 .It Sy pool_context
205 The load state for the pool (0=none, 1=open, 2=import, 3=tryimport, 4=recover
206 5=error).
207 .It Sy vdev_guid
208 The GUID of the vdev in question (the vdev failing or operated upon with
209 .Nm zpool Cm clear ,
210 etc.).
211 .It Sy vdev_type
212 Type of vdev -
213 .Sy disk ,
214 .Sy file ,
215 .Sy mirror ,
216 etc.
217 See the
218 .Sy Virtual Devices
219 section of
220 .Xr zpoolconcepts 7
221 for more information on possible values.
222 .It Sy vdev_path
223 Full path of the vdev, including any
224 .Em -partX .
225 .It Sy vdev_devid
226 ID of vdev (if any).
227 .It Sy vdev_fru
228 Physical FRU location.
229 .It Sy vdev_state
230 State of vdev (0=uninitialized, 1=closed, 2=offline, 3=removed, 4=failed to
231 open, 5=faulted, 6=degraded, 7=healthy).
232 .It Sy vdev_ashift
233 The ashift value of the vdev.
234 .It Sy vdev_complete_ts
235 The time the last I/O request completed for the specified vdev.
236 .It Sy vdev_delta_ts
237 The time since the last I/O request completed for the specified vdev.
238 .It Sy vdev_spare_paths
239 List of spares, including full path and any
240 .Em -partX .
241 .It Sy vdev_spare_guids
242 GUID(s) of spares.
243 .It Sy vdev_read_errors
244 How many read errors that have been detected on the vdev.
245 .It Sy vdev_write_errors
246 How many write errors that have been detected on the vdev.
247 .It Sy vdev_cksum_errors
248 How many checksum errors that have been detected on the vdev.
249 .It Sy parent_guid
250 GUID of the vdev parent.
251 .It Sy parent_type
252 Type of parent.
253 See
254 .Sy vdev_type .
255 .It Sy parent_path
256 Path of the vdev parent (if any).
257 .It Sy parent_devid
258 ID of the vdev parent (if any).
259 .It Sy zio_objset
260 The object set number for a given I/O request.
261 .It Sy zio_object
262 The object number for a given I/O request.
263 .It Sy zio_level
264 The indirect level for the block.
265 Level 0 is the lowest level and includes data blocks.
266 Values > 0 indicate metadata blocks at the appropriate level.
267 .It Sy zio_blkid
268 The block ID for a given I/O request.
269 .It Sy zio_err
270 The error number for a failure when handling a given I/O request,
271 compatible with
272 .Xr errno 3
273 with the value of
274 .Sy EBADE
275 used to indicate a ZFS checksum error.
276 .It Sy zio_offset
277 The offset in bytes of where to write the I/O request for the specified vdev.
278 .It Sy zio_size
279 The size in bytes of the I/O request.
280 .It Sy zio_flags
281 The current flags describing how the I/O request should be handled.
282 See the
283 .Sy I/O FLAGS
284 section for the full list of I/O flags.
285 .It Sy zio_stage
286 The current stage of the I/O in the pipeline.
287 See the
288 .Sy I/O STAGES
289 section for a full list of all the I/O stages.
290 .It Sy zio_pipeline
291 The valid pipeline stages for the I/O.
292 See the
293 .Sy I/O STAGES
294 section for a full list of all the I/O stages.
295 .It Sy zio_delay
296 The time elapsed (in nanoseconds) waiting for the block layer to complete the
297 I/O request.
298 Unlike
299 .Sy zio_delta ,
300 this does not include any vdev queuing time and is
301 therefore solely a measure of the block layer performance.
302 .It Sy zio_timestamp
303 The time when a given I/O request was submitted.
304 .It Sy zio_delta
305 The time required to service a given I/O request.
306 .It Sy prev_state
307 The previous state of the vdev.
308 .It Sy cksum_expected
309 The expected checksum value for the block.
310 .It Sy cksum_actual
311 The actual checksum value for an errant block.
312 .It Sy cksum_algorithm
313 Checksum algorithm used.
314 See
315 .Xr zfsprops 7
316 for more information on the available checksum algorithms.
317 .It Sy cksum_byteswap
318 Whether or not the data is byteswapped.
319 .It Sy bad_ranges
320 .No [\& Ns Ar start , end )
321 pairs of corruption offsets.
322 Offsets are always aligned on a 64-bit boundary,
323 and can include some gaps of non-corruption.
324 (See
325 .Sy bad_ranges_min_gap )
326 .It Sy bad_ranges_min_gap
327 In order to bound the size of the
328 .Sy bad_ranges
329 array, gaps of non-corruption
330 less than or equal to
331 .Sy bad_ranges_min_gap
332 bytes have been merged with
333 adjacent corruption.
334 Always at least 8 bytes, since corruption is detected on a 64-bit word basis.
335 .It Sy bad_range_sets
336 This array has one element per range in
337 .Sy bad_ranges .
338 Each element contains
339 the count of bits in that range which were clear in the good data and set
340 in the bad data.
341 .It Sy bad_range_clears
342 This array has one element per range in
343 .Sy bad_ranges .
344 Each element contains
345 the count of bits for that range which were set in the good data and clear in
346 the bad data.
347 .It Sy bad_set_bits
348 If this field exists, it is an array of
349 .Pq Ar bad data No & ~( Ns Ar good data ) ;
350 that is, the bits set in the bad data which are cleared in the good data.
351 Each element corresponds a byte whose offset is in a range in
352 .Sy bad_ranges ,
353 and the array is ordered by offset.
354 Thus, the first element is the first byte in the first
355 .Sy bad_ranges
356 range, and the last element is the last byte in the last
357 .Sy bad_ranges
358 range.
359 .It Sy bad_cleared_bits
360 Like
361 .Sy bad_set_bits ,
362 but contains
363 .Pq Ar good data No & ~( Ns Ar bad data ) ;
364 that is, the bits set in the good data which are cleared in the bad data.
365 .It Sy bad_set_histogram
366 If this field exists, it is an array of counters.
367 Each entry counts bits set in a particular bit of a big-endian uint64 type.
368 The first entry counts bits
369 set in the high-order bit of the first byte, the 9th byte, etc, and the last
370 entry counts bits set of the low-order bit of the 8th byte, the 16th byte, etc.
371 This information is useful for observing a stuck bit in a parallel data path,
372 such as IDE or parallel SCSI.
373 .It Sy bad_cleared_histogram
374 If this field exists, it is an array of counters.
375 Each entry counts bit clears in a particular bit of a big-endian uint64 type.
376 The first entry counts bits
377 clears of the high-order bit of the first byte, the 9th byte, etc, and the
378 last entry counts clears of the low-order bit of the 8th byte, the 16th byte,
379 etc.
380 This information is useful for observing a stuck bit in a parallel data
381 path, such as IDE or parallel SCSI.
382 .El
383 .
384 .Sh I/O STAGES
385 The ZFS I/O pipeline is comprised of various stages which are defined below.
386 The individual stages are used to construct these basic I/O
387 operations: Read, Write, Free, Claim, and Ioctl.
388 These stages may be
389 set on an event to describe the life cycle of a given I/O request.
390 .Pp
391 .TS
392 tab(:);
393 l l l .
394 Stage:Bit Mask:Operations
395 _:_:_
396 ZIO_STAGE_OPEN:0x00000001:RWFCI
397
398 ZIO_STAGE_READ_BP_INIT:0x00000002:R----
399 ZIO_STAGE_WRITE_BP_INIT:0x00000004:-W---
400 ZIO_STAGE_FREE_BP_INIT:0x00000008:--F--
401 ZIO_STAGE_ISSUE_ASYNC:0x00000010:RWF--
402 ZIO_STAGE_WRITE_COMPRESS:0x00000020:-W---
403
404 ZIO_STAGE_ENCRYPT:0x00000040:-W---
405 ZIO_STAGE_CHECKSUM_GENERATE:0x00000080:-W---
406
407 ZIO_STAGE_NOP_WRITE:0x00000100:-W---
408
409 ZIO_STAGE_DDT_READ_START:0x00000200:R----
410 ZIO_STAGE_DDT_READ_DONE:0x00000400:R----
411 ZIO_STAGE_DDT_WRITE:0x00000800:-W---
412 ZIO_STAGE_DDT_FREE:0x00001000:--F--
413
414 ZIO_STAGE_GANG_ASSEMBLE:0x00002000:RWFC-
415 ZIO_STAGE_GANG_ISSUE:0x00004000:RWFC-
416
417 ZIO_STAGE_DVA_THROTTLE:0x00008000:-W---
418 ZIO_STAGE_DVA_ALLOCATE:0x00010000:-W---
419 ZIO_STAGE_DVA_FREE:0x00020000:--F--
420 ZIO_STAGE_DVA_CLAIM:0x00040000:---C-
421
422 ZIO_STAGE_READY:0x00080000:RWFCI
423
424 ZIO_STAGE_VDEV_IO_START:0x00100000:RW--I
425 ZIO_STAGE_VDEV_IO_DONE:0x00200000:RW--I
426 ZIO_STAGE_VDEV_IO_ASSESS:0x00400000:RW--I
427
428 ZIO_STAGE_CHECKSUM_VERIFY:0x00800000:R----
429
430 ZIO_STAGE_DONE:0x01000000:RWFCI
431 .TE
432 .
433 .Sh I/O FLAGS
434 Every I/O request in the pipeline contains a set of flags which describe its
435 function and are used to govern its behavior.
436 These flags will be set in an event as a
437 .Sy zio_flags
438 payload entry.
439 .Pp
440 .TS
441 tab(:);
442 l l .
443 Flag:Bit Mask
444 _:_
445 ZIO_FLAG_DONT_AGGREGATE:0x00000001
446 ZIO_FLAG_IO_REPAIR:0x00000002
447 ZIO_FLAG_SELF_HEAL:0x00000004
448 ZIO_FLAG_RESILVER:0x00000008
449 ZIO_FLAG_SCRUB:0x00000010
450 ZIO_FLAG_SCAN_THREAD:0x00000020
451 ZIO_FLAG_PHYSICAL:0x00000040
452
453 ZIO_FLAG_CANFAIL:0x00000080
454 ZIO_FLAG_SPECULATIVE:0x00000100
455 ZIO_FLAG_CONFIG_WRITER:0x00000200
456 ZIO_FLAG_DONT_RETRY:0x00000400
457 ZIO_FLAG_DONT_CACHE:0x00000800
458 ZIO_FLAG_NODATA:0x00001000
459 ZIO_FLAG_INDUCE_DAMAGE:0x00002000
460
461 ZIO_FLAG_IO_ALLOCATING:0x00004000
462 ZIO_FLAG_IO_RETRY:0x00008000
463 ZIO_FLAG_PROBE:0x00010000
464 ZIO_FLAG_TRYHARD:0x00020000
465 ZIO_FLAG_OPTIONAL:0x00040000
466
467 ZIO_FLAG_DONT_QUEUE:0x00080000
468 ZIO_FLAG_DONT_PROPAGATE:0x00100000
469 ZIO_FLAG_IO_BYPASS:0x00200000
470 ZIO_FLAG_IO_REWRITE:0x00400000
471 ZIO_FLAG_RAW_COMPRESS:0x00800000
472 ZIO_FLAG_RAW_ENCRYPT:0x01000000
473
474 ZIO_FLAG_GANG_CHILD:0x02000000
475 ZIO_FLAG_DDT_CHILD:0x04000000
476 ZIO_FLAG_GODFATHER:0x08000000
477 ZIO_FLAG_NOPWRITE:0x10000000
478 ZIO_FLAG_REEXECUTED:0x20000000
479 ZIO_FLAG_DELEGATED:0x40000000
480 ZIO_FLAG_FASTWRITE:0x80000000
481 .TE
482 .
483 .Sh SEE ALSO
484 .Xr zfs 4 ,
485 .Xr zed 8 ,
486 .Xr zpool-wait 8
Cache object: ef6ed6ade98a7a8bfd31a33fa9e977dc
|