Lines Matching full:filesystem
7 mke2fs \- create an ext2/ext3/ext4 filesystem
143 is used to create an ext2, ext3, or ext4 filesystem, usually in a disk
157 The defaults of the parameters for the newly created filesystem, if not
168 block-size is heuristically determined by the filesystem size and
169 the expected usage of the filesystem (see the
188 Set extended options for the filesystem. Extended options are comma
202 Configure the filesystem for a RAID array with
204 filesystem blocks. This is the number of blocks read or written to disk
207 This mostly affects placement of filesystem metadata like bitmaps at
213 Configure the filesystem for a RAID array with
215 filesystem blocks per stripe. This is typically stride-size * N, where
223 to support a filesystem that has
231 This speeds up filesystem
233 initializing the filesystem in the background when the filesystem is
238 Set a flag in the filesystem superblock indicating that it may be
239 mounted using experimental kernel code, such as the ext4dev filesystem.
246 zeroed. This significantly speeds up filesystem initialization. This is set
259 to create a filesystem, even if the specified device is not a partition
263 to create a filesystem even if the filesystem appears to be in use
270 for the filesystem. (For administrators who are creating
282 ext4 filesystem. This improves meta-data locality and performance
286 filesystem feature is enabled.
296 be smaller than the blocksize of the filesystem, since in that case more
299 of inodes on a filesystem after it is created, so be careful deciding the
313 space in the filesystem and can also negatively impact performance.
317 possible to change this value after the filesystem is created.
320 Create the filesystem with an ext3 journal. If the
323 create an appropriately sized journal (given the size of the filesystem)
324 stored within the filesystem. Note that you must be using a kernel
335 Create an internal journal (i.e., stored inside the filesystem) of size
338 The size of the journal must be at least 1024 filesystem blocks
340 and may be no more than 102,400 filesystem blocks.
343 @JDEV@Attach the filesystem to the journal block device located on
354 @JDEV@same block size as the new filesystem.
378 @JDEV@options can be given for a filesystem.
398 Set the volume label for the filesystem to
404 Specify the percentage of the filesystem blocks reserved for
409 prevented from writing to the filesystem. The default percentage
413 Set the last mounted directory for the filesystem. This might be useful
415 determine where the filesystem should be mounted.
420 to not actually create a filesystem, but display what it
421 would do if it were to create a filesystem. This can be used to
423 filesystem, so long as the
426 filesystem was originally created are used again. (With the
432 reserved for the filesystem (which is based on the number of blocks and
440 filesystem. The creator field is set by default to the name of the OS the
445 Create a filesystem with the given features (filesystem options),
446 overriding the default filesystem options. The features that are
462 subsections for the filesystem and usage types. See the
465 The filesystem type-specific configuration setting found in the
470 The filesystem feature set will be further edited
474 relation for the filesystem type being created, or in the
478 The filesystem feature set is comprised of a list of features, separated
481 pseudo-filesystem feature "none" will clear all filesystem features.
490 efficient encoding which speeds up filesystem access, especially for
513 @JDEV@instead of a regular ext2 filesystem.
520 Filesystem can contain files that are greater than 2GB. (Modern kernels
530 filesystem may grow to 1024 times its initial size. This can be changed
536 Create a filesystem with fewer superblock backup copies
540 Create a filesystem without initializing all of the block groups. This
543 speed up filesystem creation time noticeably (if lazy_itable_init is
546 time dramatically. It is only supported by the ext4 filesystem in
556 Set the filesystem revision for the new filesystem. Note that 1.2
571 specify the correct filesystem blocksize when using this option,
579 filesystem type (i.e., ext2, ext3, ext4, etc.) that is to be created.
586 file. This option controls which filesystem options are used by
594 option is used to explicitly add or remove filesystem options that
595 should be set in the newly created filesystem, the
596 resulting filesystem may not be supported by the requested
599 filesystem that is not supported by the ext3 implementation as found in
601 will create a filesystem that does not have a journal and hence will not
602 be supported by the ext3 filesystem code in the Linux kernel.)
605 Specify how the filesystem is going to be used, so that
607 can choose optimal filesystem parameters for that use. The usage
615 will pick a single default usage type based on the size of the filesystem to
616 be created. If the filesystem size is less than or equal to 3 megabytes,
618 will use the filesystem type
620 If the filesystem size is greater than 3 but less than or equal to
623 will use the filesystem
627 will use the default filesystem type
631 Create the filesystem with the specified UUID.
