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``
141 	An XFS filesystem has up to three parts: a data section, a log
153 	The filesystem will be mounted without running log recovery.
154 	If the filesystem was not cleanly unmounted, it is likely to
168 	within the filesystem.
189 	with the existing filesystem alignment characteristics.  In
205 	When specified, all filesystem namespace operations are
216 The V4 filesystem format lacks certain features that are supported by
222 Administrators and users can detect a V4 filesystem by running xfs_info
223 against a filesystem mountpoint and checking for a string containing
242 Mounting with V4 filesystem     September 2030
243 Mounting ascii-ci filesystem    September 2030
266 The following sysctls are available for the XFS filesystem:
273 	The interval at which the filesystem flushes metadata
277 	The interval at which the filesystem ages filestreams cache
293 	This will generate detailed messages & backtraces for filesystem
391 	error is found during the filesystem operation. It can propagate
403 The filesystem behavior during an error can be set via ``sysfs`` files. Each
408 The action taken by the filesystem when the error is propagated is context
415 mounted filesystem:
421 	The short device name of the mounted filesystem. This is the same device
434 Each filesystem has "global" error configuration options defined in their top
440 	Defines the filesystem error behavior at unmount time.
450 	filesystem from ever unmounting fully in the case of "retry forever"
455 	removed by the unmounting filesystem before a "retry forever" error
456 	handler configuration causes unmount to hang, and hence the filesystem
460 Each filesystem has specific error class handlers that define the error
471 	the filesystem will propagate the error. The retry count for a given
485 	Define the amount of time (in seconds) that the filesystem is
516 The control knobs for a filesystem's workqueues are organized by task at hand
524   xfs_iwalk-$pid  Inode scans of the entire filesystem. Currently limited to