Lines Matching full:filesystem
7 mke2fs \- create an ext2/ext3/ext4 filesystem
146 is used to create an ext2, ext3, or ext4 filesystem, usually in a disk
160 The defaults of the parameters for the newly created filesystem, if not
171 block-size is heuristically determined by the filesystem size and
172 the expected usage of the filesystem (see the
206 Set extended options for the filesystem. Extended options are comma
230 Configure the filesystem for a RAID array with
232 filesystem blocks. This is the number of blocks read or written to disk
235 This mostly affects placement of filesystem metadata like bitmaps at
241 Configure the filesystem for a RAID array with
243 filesystem blocks per stripe. This is typically stride-size * N, where
251 to support a filesystem that has
259 This speeds up filesystem
261 initializing the filesystem in the background when the filesystem is
268 This speeds up filesystem initialization noticeably, but carries some
280 filesystem to change based on the user running \fBmke2fs\fR.
283 Set a flag in the filesystem superblock indicating that it may be
284 mounted using experimental kernel code, such as the ext4dev filesystem.
291 zeroed. This significantly speeds up filesystem initialization. This is set
311 to create a filesystem, even if the specified device is not a partition
315 to create a filesystem even if the filesystem appears to be in use
322 for the filesystem. (For administrators who are creating
338 ext4 filesystem. This improves meta-data locality and performance
342 filesystem feature is enabled.
352 be smaller than the blocksize of the filesystem, since in that case more
354 possible to change this ratio on a filesystem after it is created, so be
356 a filesystem changes the numer of inodes to maintain this ratio.
365 space in the filesystem and can also negatively impact performance.
367 possible to change this value after the filesystem is created.
386 Create the filesystem with an ext3 journal. If the
389 create an appropriately sized journal (given the size of the filesystem)
390 stored within the filesystem. Note that you must be using a kernel
401 Create an internal journal (i.e., stored inside the filesystem) of size
404 The size of the journal must be at least 1024 filesystem blocks
406 and may be no more than 10,240,000 filesystem blocks or half the total
410 @JDEV@Attach the filesystem to the journal block device located on
421 @JDEV@same block size as the new filesystem.
445 @JDEV@options can be given for a filesystem.
465 Set the volume label for the filesystem to
471 Specify the percentage of the filesystem blocks reserved for
476 prevented from writing to the filesystem. The default percentage
480 Set the last mounted directory for the filesystem. This might be useful
482 determine where the filesystem should be mounted.
487 to not actually create a filesystem, but display what it
488 would do if it were to create a filesystem. This can be used to
490 filesystem, so long as the
493 filesystem was originally created are used again. (With the
499 reserved for the filesystem (which is based on the number of blocks and
507 filesystem. The creator field is set by default to the name of the OS the
512 Create a filesystem with the given features (filesystem options),
513 overriding the default filesystem options. The features that are
529 subsections for the filesystem and usage types. See the
532 The filesystem type-specific configuration setting found in the
537 The filesystem feature set will be further edited
541 relation for the filesystem type being created, or in the
545 The filesystem feature set is comprised of a list of features, separated
549 The pseudo-filesystem feature "none" will clear all filesystem features.
561 Set the filesystem revision for the new filesystem. Note that 1.2
576 specify the correct filesystem blocksize when using this option,
584 Specify the filesystem type (i.e., ext2, ext3, ext4, etc.) that is
592 file. This option controls which filesystem options are used by
600 option is used to explicitly add or remove filesystem options that
601 should be set in the newly created filesystem, the
602 resulting filesystem may not be supported by the requested
605 filesystem that is not supported by the ext3 implementation as found in
607 will create a filesystem that does not have a journal and hence will not
608 be supported by the ext3 filesystem code in the Linux kernel.)
611 Specify how the filesystem is going to be used, so that
613 can choose optimal filesystem parameters for that use. The usage
621 will pick a single default usage type based on the size of the filesystem to
622 be created. If the filesystem size is less than or equal to 3 megabytes,
624 will use the filesystem type
626 If the filesystem size is greater than 3 but less than or equal to
629 will use the filesystem type
631 If the filesystem size is greater than or equal to 4 terabytes but less than
634 will use the filesystem type
636 If the filesystem size is greater than or equal to 16 terabytes,
638 will use the filesystem type
642 will use the default filesystem type
646 Create the filesystem with the specified UUID.
676 If set, do not show the message of filesystem automatic check caused by
