Lines Matching full:errors

179 additional conditions that result in I/O errors.
198 * Unaligned write errors: These errors result from the host issuing write
201   enforces sequential file write for sequential zones, unaligned write errors
208 * Delayed write errors: similarly to regular block devices, if the device side
209   write cache is enabled, write errors may occur in ranges of previously
212   errors can propagate through a stream of cached sequential data for a zone
215 All I/O errors detected by zonefs are notified to the user with an error code
217 actions taken by zonefs in response to I/O errors depend on the I/O type (read
221 * For read I/O errors, zonefs does not execute any particular recovery action,
226 * For write I/O errors, zonefs I/O error recovery is always executed.
235   Immediate or delayed write errors in a sequential zone file may cause the file
256 with the "errors=xxx" mount option. The table below summarizes the result of
262     | "errors=xxx" |  device   |                 access permissions      |
285 * The "errors=remount-ro" mount option is the default behavior of zonefs I/O
286   error processing if no errors mount option is specified.
287 * With the "errors=remount-ro" mount option, the change of the file access
310 * errors=<behavior>
313 "errors=<behavior>" option
316 The "errors=<behavior>" option mount option allows the user to specify zonefs
317 behavior in response to I/O errors, inode size inconsistencies or zone
326 previous section. Mount time I/O errors will cause the mount operation to fail.
342 translates into a risk for applications to see write IO errors due to this
346 To avoid these potential errors, the "explicit-open" mount option forces zones
378   sequential zone files.  Failure to do so can result in write errors.