mirror of https://github.com/vitalif/e2fsprogs
Fix spelling typo's in man pages for tune2fs and mke2fs
Addresses-Debian-Bug: #680114 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>bitmap-optimize
parent
280841e878
commit
585545e1ee
|
@ -201,7 +201,7 @@ filesystem check (discarding blocks is useful on solid state devices and sparse
|
||||||
filesystem has been fully checked and only if it does not contain recognizable
|
filesystem has been fully checked and only if it does not contain recognizable
|
||||||
errors. However there might be cases where
|
errors. However there might be cases where
|
||||||
.B e2fsck
|
.B e2fsck
|
||||||
does not fully recognise a problem and hence in this case this
|
does not fully recognize a problem and hence in this case this
|
||||||
option may prevent you from further manual data recovery.
|
option may prevent you from further manual data recovery.
|
||||||
.TP
|
.TP
|
||||||
.BI nodiscard
|
.BI nodiscard
|
||||||
|
|
|
@ -103,8 +103,8 @@ program.
|
||||||
.PP
|
.PP
|
||||||
The
|
The
|
||||||
.I device
|
.I device
|
||||||
specifer can either be a filename (i.e., /dev/sda1), or a LABEL or UUID
|
specifier can either be a filename (i.e., /dev/sda1), or a LABEL or UUID
|
||||||
specifer: "\fBLABEL=\fIvolume-name\fR" or "\fBUUID=\fIuuid\fR". (i.e.,
|
specifier: "\fBLABEL=\fIvolume-name\fR" or "\fBUUID=\fIuuid\fR". (i.e.,
|
||||||
LABEL=home or UUID=e40486c6-84d5-4f2f-b99c-032281799c9d).
|
LABEL=home or UUID=e40486c6-84d5-4f2f-b99c-032281799c9d).
|
||||||
.SH OPTIONS
|
.SH OPTIONS
|
||||||
.TP
|
.TP
|
||||||
|
@ -432,8 +432,8 @@ The following mount options can be set or cleared using
|
||||||
Enable debugging code for this filesystem.
|
Enable debugging code for this filesystem.
|
||||||
.TP
|
.TP
|
||||||
.B bsdgroups
|
.B bsdgroups
|
||||||
Emulate BSD behaviour when creating new files: they will take the group-id
|
Emulate BSD behavior when creating new files: they will take the group-id
|
||||||
of the directory in which they were created. The standard System V behaviour
|
of the directory in which they were created. The standard System V behavior
|
||||||
is the default, where newly created files take on the fsgid of the current
|
is the default, where newly created files take on the fsgid of the current
|
||||||
process, unless the directory has the setgid bit set, in which case it takes
|
process, unless the directory has the setgid bit set, in which case it takes
|
||||||
the gid from the parent directory, and also gets the setgid bit set if it is
|
the gid from the parent directory, and also gets the setgid bit set if it is
|
||||||
|
@ -481,7 +481,7 @@ currently only supported by the ext4 file system driver in 2.6.35+
|
||||||
kernels.)
|
kernels.)
|
||||||
.TP
|
.TP
|
||||||
.B discard
|
.B discard
|
||||||
The file system will be mouinted with the discard mount option. This will
|
The file system will be mounted with the discard mount option. This will
|
||||||
cause the file system driver to attempt to use the trim/discard feature
|
cause the file system driver to attempt to use the trim/discard feature
|
||||||
of some storage devices (such as SSD's and thin-provisioned drives
|
of some storage devices (such as SSD's and thin-provisioned drives
|
||||||
available in some enterprise storage arrays) to inform the storage
|
available in some enterprise storage arrays) to inform the storage
|
||||||
|
@ -521,7 +521,7 @@ Allow bitmaps and inode tables for a block group to be placed
|
||||||
anywhere on the storage media. \fBTune2fs\fR will not reorganize
|
anywhere on the storage media. \fBTune2fs\fR will not reorganize
|
||||||
the location of the inode tables and allocation bitmaps, as
|
the location of the inode tables and allocation bitmaps, as
|
||||||
.BR mke2fs (8)
|
.BR mke2fs (8)
|
||||||
will do when it creates a freshly formated file system with
|
will do when it creates a freshly formatted file system with
|
||||||
.B flex_bg
|
.B flex_bg
|
||||||
enabled.
|
enabled.
|
||||||
.TP
|
.TP
|
||||||
|
|
Loading…
Reference in New Issue