Lines Matching full:filesystem

4 The SGI XFS Filesystem
7 XFS is a high performance journaling filesystem which originated
22 When mounting an XFS filesystem, the following options are accepted.
48 	by the filesystem.
55 	device reclaim space freed by the filesystem.  This is
75 	across the entire filesystem rather than just on directories
90 	to create inodes at any location in the filesystem,
108 	If ``largeio`` is specified, a filesystem that was created with a
110 	in ``st_blksize``. If the filesystem does not have a ``swidth``
149 	An XFS filesystem has up to three parts: a data section, a log
169 	The filesystem will be mounted without running log recovery.
170 	If the filesystem was not cleanly unmounted, it is likely to
184 	within the filesystem.
205 	with the existing filesystem alignment characteristics.  In
221 	When specified, all filesystem namespace operations are
232 The V4 filesystem format lacks certain features that are supported by
238 Administrators and users can detect a V4 filesystem by running xfs_info
239 against a filesystem mountpoint and checking for a string containing
258 Mounting with V4 filesystem     September 2030
259 Mounting ascii-ci filesystem    September 2030
282 The following sysctls are available for the XFS filesystem:
289 	The interval at which the filesystem flushes metadata
293 	The interval at which the filesystem ages filestreams cache
309 	This will generate detailed messages & backtraces for filesystem
407 	error is found during the filesystem operation. It can propagate
419 The filesystem behavior during an error can be set via ``sysfs`` files. Each
424 The action taken by the filesystem when the error is propagated is context
431 mounted filesystem:
437 	The short device name of the mounted filesystem. This is the same device
450 Each filesystem has "global" error configuration options defined in their top
456 	Defines the filesystem error behavior at unmount time.
466 	filesystem from ever unmounting fully in the case of "retry forever"
471 	removed by the unmounting filesystem before a "retry forever" error
472 	handler configuration causes unmount to hang, and hence the filesystem
476 Each filesystem has specific error class handlers that define the error
487 	the filesystem will propagate the error. The retry count for a given
501 	Define the amount of time (in seconds) that the filesystem is
532 The control knobs for a filesystem's workqueues are organized by task at hand
540   xfs_iwalk-$pid  Inode scans of the entire filesystem. Currently limited to