Lines Matching +full:- +full:- +full:retry +full:- +full:all +full:- +full:errors
1 .. SPDX-License-Identifier: GPL-2.0
8 on the SGI IRIX platform. It is completely multi-threaded, can
15 for further details. This implementation is on-disk compatible
25 Sets the buffered I/O end-of-file preallocation size when
28 through to 1GiB, inclusive, in power-of-2 increments.
30 The default behaviour is for dynamic end-of-file
40 on-disk. When the new form is used for the first time when
42 attributes) the on-disk superblock feature bit field will be
45 The default behaviour is determined by the on-disk feature
116 Set the number of in-memory log buffers. Valid numbers
117 range from 2-8 inclusive.
128 Set the size of each in-memory log buffer. The size may be
140 Use an external log (metadata journal) and/or real-time device.
142 section, and a real-time section. The real-time section is
149 with non-zero data alignment parameters (``sunit``, ``swidth``) by
157 Filesystems mounted ``norecovery`` must be mounted read-only or
164 read-only snapshots.
167 Forcibly turns off all quota accounting and enforcement
184 or a stripe volume. "value" must be specified in 512-byte
186 that were created with non-zero data alignment parameters.
191 increasing it by a power-of-2 multiple. Valid ``swidth`` values
205 When specified, all filesystem namespace operations are
219 Because of this, the V4 format is deprecated. All users should upgrade
243 Mounting ascii-ci filesystem September 2030
278 references and returns timed-out AGs back to the free stream
292 A volume knob for error reporting when internal errors occur.
302 OR together the tags which represent errors which should cause panics:
389 -failure speed:
393 or simply retry forever.
395 -error classes:
400 -error handlers:
404 error handler works independently - the first condition met by an error handler
409 dependent - it may cause a shut down in the case of an unrecoverable error,
428 - "metadata": applies metadata buffer write IO
442 If set to a value of 1, XFS will override all other error configurations
444 i.e. no retries, no retry timeout. This will always allow unmount to
445 succeed when there are persistent errors present.
447 If set to 0, the configured retry behaviour will continue until all
449 completion when there are persistent errors, and it may prevent the
450 filesystem from ever unmounting fully in the case of "retry forever"
455 removed by the unmounting filesystem before a "retry forever" error
461 propagation behaviour for specific errors. There is also a "default" error
462 handler defined, which defines the behaviour for all errors that don't have
463 specific handlers defined. Where multiple retry constraints are configured for
464 a single error, the first retry configuration that expires will cause the error
469 max_retries (Min: -1 Default: Varies Max: INTMAX)
471 the filesystem will propagate the error. The retry count for a given
475 Setting the value to "-1" will cause XFS to retry forever for this
481 Setting the value to "N" (where 0 < N < Max) will make XFS retry the
484 retry_timeout_seconds (Min: -1 Default: Varies Max: 1 day)
486 allowed to retry its operations when the specific error is
489 Setting the value to "-1" will allow XFS to retry forever for this
495 Setting the value to "N" (where 0 < N < Max) will allow XFS to retry the
500 "metadata/ENODEV" are "0" rather than "-1" so that this error handler defaults
517 and the short name of the data device. They all can be found in:
524 xfs_iwalk-$pid Inode scans of the entire filesystem. Currently limited to
526 xfs-gc Background garbage collection of disk space that have been
532 found in /sys/bus/workqueue/devices/xfs_iwalk-1111!nvme0n1/.