Documentation/admin-guide/xfs.rst

7 XFS is a high performance journaling filesystem which originated
22 When mounting an XFS filesystem, the following options are accepted.
39 	device reclaim space freed by the filesystem.  This is
59 	across the entire filesystem rather than just on directories
68 	to create inodes at any location in the filesystem,
86 	If ``largeio`` is specified, a filesystem that was created with a
88 	in ``st_blksize``. If the filesystem does not have a ``swidth``
127 	An XFS filesystem has up to three parts: a data section, a log
158 	The filesystem will be mounted without running log recovery.
159 	If the filesystem was not cleanly unmounted, it is likely to
173 	within the filesystem.
194 	with the existing filesystem alignment characteristics.  In
210 	When specified, all filesystem namespace operations are
229 The V4 filesystem format lacks certain features that are supported by
235 Administrators and users can detect a V4 filesystem by running xfs_info
236 against a filesystem mountpoint and checking for a string containing
254 Mounting with V4 filesystem     September 2030
255 Mounting ascii-ci filesystem    September 2030
278 The following sysctls are available for the XFS filesystem:
285 	The interval at which the filesystem flushes metadata
289 	The interval at which the filesystem ages filestreams cache
302 	This will generate detailed messages & backtraces for filesystem
385 	error is found during the filesystem operation. It can propagate
397 The filesystem behavior during an error can be set via ``sysfs`` files. Each
402 The action taken by the filesystem when the error is propagated is context
409 mounted filesystem:
415 	The short device name of the mounted filesystem. This is the same device
428 Each filesystem has "global" error configuration options defined in their top
434 	Defines the filesystem error behavior at unmount time.
444 	filesystem from ever unmounting fully in the case of "retry forever"
449 	removed by the unmounting filesystem before a "retry forever" error
450 	handler configuration causes unmount to hang, and hence the filesystem
454 Each filesystem has specific error class handlers that define the error
465 	the filesystem will propagate the error. The retry count for a given
479 	Define the amount of time (in seconds) that the filesystem is
510 The control knobs for a filesystem's workqueues are organized by task at hand
518   xfs_iwalk-$pid  Inode scans of the entire filesystem. Currently limited to