Lines Matching full:system
7 tune2fs \- adjust tunable file system parameters on ext2/ext3/ext4 file systems
98 allows the system administrator to adjust various tunable file system
116 Adjust the number of mounts after which the file system will be checked by
123 is 0 or \-1, the number of times the file system is mounted will be disregarded
134 are concerned about file system corruptions caused by potential hardware
138 program. This does require placing the file system on an LVM volume,
142 Set the number of times the file system has been mounted.
148 will check the file system at the next reboot.
152 In all cases, a file system error will cause
154 to check the file system on the next boot.
163 Remount file system read-only.
170 Set extended options for the file system. Extended options are comma
178 fscked, or major file system corruption can result. Needs '-f'.
191 Configure the file system for a RAID array with
193 file system blocks. This is the number of blocks read or written to disk
194 before moving to next disk. This mostly affects placement of file system
201 Configure the file system for a RAID array with
203 file system blocks per stripe. This is typically be stride-size * N, where
235 which means that invalid strings should be rejected by the file system.
242 system is mounted. Unlike the bitmask-based default mount options which
250 The ext4 file system driver will first apply
258 and not at all by the ext2 and ext3 file system drivers.
261 Set a flag in the file system superblock indicating that errors have been found.
265 Set a flag in the file system superblock indicating that it may be
266 mounted using experimental kernel code, such as the ext4dev file system.
269 Clear the test_fs flag, indicating the file system should only be mounted
270 using production-level file system code.
277 file system feature from a file system which has
280 external journal is not available. If the file system appears to require
286 Removing an external journal from a file system which was not cleanly unmounted
288 severe data loss and file system corruption.
291 Set the group which can use the reserved file system blocks.
298 Adjust the maximal time between two file system checks.
315 Change the inode size used by the file system. This requires rewriting
316 the inode table, so it requires that the file system is checked for
319 This operation can also take a while and the file system can be
321 converting the file system. Backing up the file system before changing
330 Add an ext3 journal to the file system. If the
333 an appropriately sized journal (given the size of the file system)
334 stored within the file system. Note that you must be using a kernel
337 If this option is used to create a journal on a mounted file system, an
340 will be created in the top-level directory of the file system, as it is
341 the only safe way to create the journal inode while the file system is
343 delete it, or modify it while the file system is mounted; for this
350 except for the root file system, this should happen automatically and
351 naturally during the next reboot cycle. Since the root file system is
357 the initrd scripts will automatically convert an ext2 root file system
360 file specifies the ext3 file system for the root file system in order to
362 the root file system.
371 Create a journal stored in the file system of size
373 megabytes. The size of the journal must be at least 1024 file system blocks
375 and may be no more than 10,240,000 file system blocks.
376 There must be enough free space in the file system to create a journal of
386 on the file system. If this option is not specified and if
397 10,240,000 file system blocks or half the total file system size
405 beginning of the file system.
408 @JDEV@Attach the file system to the journal block device located on
443 @JDEV@options can be given for a file system.
446 List the contents of the file system superblock, including the current
450 Set the volume label of the file system.
451 Ext2 file system labels can be at most 16 characters long; if
467 Set the percentage of the file system which may only be allocated
468 by privileged processes. Reserving some number of file system blocks
470 to avoid file system fragmentation, and to allow system
474 prevented from writing to the file system. Normally, the default percentage
478 Set the last-mounted directory for the file system.
481 Set or clear the indicated default mount options in the file system.
493 caret character ('^') will be cleared in the file system's superblock;
495 character ('+') will be added to the file system.
502 Enable debugging code for this file system.
506 of the directory in which they were created. The standard System V behavior
523 When the file system is mounted with journaling enabled, all data
525 into the main file system.
528 When the file system is mounted with journaling enabled, all data is forced
529 directly out to the main file system prior to its metadata being committed
533 When the file system is mounted with journaling enabled, data may be
534 written into the main file system after its metadata has been committed
539 The file system will be mounted with barrier operations in the journal
541 system driver in 2.6.35+ kernels.)
544 The file system will be mounted with the block_validity option enabled,
546 the file system. This prevents corrupted metadata blocks from causing
547 file system damage by overwriting parts of the inode table or block
550 currently only supported by the ext4 file system driver in 2.6.35+
554 The file system will be mounted with the discard mount option. This will
555 cause the file system driver to attempt to use the trim/discard feature
560 system driver in 2.6.35+ kernels.)
563 The file system will be mounted with the nodelalloc mount option. This
565 only supported by the ext4 file system driver in 2.6.35+ kernels.)
569 Set or clear the indicated file system features (options) in the file system.
570 More than one file system feature can be cleared or set by separating
571 features with commas. File System features prefixed with a
572 caret character ('^') will be cleared in the file system's superblock;
573 file system features without a prefix character or prefixed with a plus
574 character ('+') will be added to the file system. For a detailed
575 description of the file system features, please see the man page
578 The following file system features can be set or cleared using
583 Enable the file system to be larger than 2^32 blocks.
586 Enable support for file system level casefolding.
588 currently only supports setting this file system feature.
601 currently only supports setting this file system feature.
604 Enable support for file system level encryption.
606 currently only supports setting this file system feature.
611 currently only supports setting this file system feature.
624 will do when it creates a freshly formatted file system with
629 Use a journal to ensure file system consistency even across unclean shutdowns.
630 Setting the file system feature is equivalent to using the
641 currently only supports setting this file system feature.
647 File System can contain files that are greater than 2GB.
653 Allow the file system to store the metadata checksum seed in the
654 superblock, enabling the administrator to change the UUID of a file system
666 Enable internal file system quota inodes.
669 Force the kernel to mount the file system read-only.
675 only supports clearing this file system feature.
680 currently only supports setting this file system feature.
683 Prevent the file system from being shrunk or having its UUID changed, in order to
687 currently only supports setting this file system feature.
691 keep a high watermark for the unused inodes in a file system, to reduce
695 original time, depending on how full the file system is.
700 currently only supports setting this file system feature.
709 file system features,
710 the file system may require being checked using
712 to return the file system to a consistent state.
714 will print a message requesting that the system administrator run
721 Enabling certain file system features may prevent the file system from being
726 features are only supported by the ext4 file system.
729 Set the number of reserved file system blocks.
747 Set the time the file system was last checked using
751 a consistent snapshot of a file system, and then check the file system
753 hardware problems, etc. If the file system was clean, then this option can
754 be used to set the last checked time on the original file system. The format
764 Set the user who can use the reserved file system blocks.
770 Set the universally unique identifier (UUID) of the file system to
781 clear the file system UUID
803 If the system does not have a good random number generator such as
811 Before overwriting a file system block, write the old contents of the block to
813 contents of the file system should something go wrong. If the empty string is
818 WARNING: The undo file cannot be used to recover from a power or system crash.