• Home
  • Raw
  • Download

Lines Matching full:error

292 	A volume knob for error reporting when internal errors occur.
301 Causes certain error conditions to call BUG(). Value is a bitmask;
382 Error handling
385 XFS can act differently according to the type of error found during its
386 operation. The implementation introduces the following concepts to the error
390 Defines how fast XFS should propagate an error upwards when a specific
391 error is found during the filesystem operation. It can propagate
395 -error classes:
396 Specifies the subsystem the error configuration will apply to, such as
398 different error handlers for which behaviour can be configured.
400 -error handlers:
401 Defines the behavior for a specific error.
403 The filesystem behavior during an error can be set via ``sysfs`` files. Each
404 error handler works independently - the first condition met by an error handler
405 for a specific class will cause the error to be propagated rather than reset and
408 The action taken by the filesystem when the error is propagated is context
409 dependent - it may cause a shut down in the case of an unrecoverable error,
411 there's nothing useful we can with the error or anyone we can report it to (e.g.
417 /sys/fs/xfs/<dev>/error/<class>/<error>/
422 name that shows up in XFS kernel error messages as "XFS(<dev>): ..."
425 The subsystem the error configuration belongs to. As of 4.9, the defined
430 <error>
431 The individual error handler configurations.
434 Each filesystem has "global" error configuration options defined in their top
437 /sys/fs/xfs/<dev>/error/
440 Defines the filesystem error behavior at unmount time.
442 If set to a value of 1, XFS will override all other error configurations
455 removed by the unmounting filesystem before a "retry forever" error
460 Each filesystem has specific error class handlers that define the error
461 propagation behaviour for specific errors. There is also a "default" error
464 a single error, the first retry configuration that expires will cause the error
467 /sys/fs/xfs/<dev>/error/<class>/<error>/
470 Defines the allowed number of retries of a specific error before
471 the filesystem will propagate the error. The retry count for a given
472 error context (e.g. a specific metadata buffer) is reset every time
476 specific error.
479 specific error is reported.
482 operation "N" times before propagating the error.
486 allowed to retry its operations when the specific error is
490 specific error.
493 specific error is reported.
496 operation for up to "N" seconds before propagating the error.
498 **Note:** The default behaviour for a specific error handler is dependent on both
499 the class and error context. For example, the default values for
500 "metadata/ENODEV" are "0" rather than "-1" so that this error handler defaults
502 unrecoverable error no matter how many times the metadata IO is retried.