e2fsck: mark that we don't care about the return value of e2fsck_lookup()

[tools/e2fsprogs.git] / resize / resize2fs.8.in

diff --git a/resize/resize2fs.8.in b/resize/resize2fs.8.in
index ae36577..528b626 100644 (file)
--- a/resize/resize2fs.8.in
+++ b/resize/resize2fs.8.in
@@ -32,18 +32,18 @@ The
 program will resize ext2, ext3, or ext4 file systems.  It can be used to
 enlarge or shrink an unmounted file system located on
 .IR device .
-If the filesystem is mounted, it can be used to expand the size of the
-mounted filesystem, assuming the kernel and the file system supports
+If the file system is mounted, it can be used to expand the size of the
+mounted file system, assuming the kernel and the file system supports
 on-line resizing.  (Modern Linux 2.6 kernels will support on-line resize
 for file systems mounted using ext3 and ext4; ext3 file systems will
 require the use of file systems with the resize_inode feature enabled.)
 .PP
 The
 .I size
-parameter specifies the requested new size of the filesystem.
+parameter specifies the requested new size of the file system.
 If no units are specified, the units of the
 .I size
-parameter shall be the filesystem blocksize of the filesystem.
+parameter shall be the file system blocksize of the file system.
 Optionally, the
 .I size
 parameter may be suffixed by one of the following units
@@ -51,7 +51,7 @@ designators: 'K', 'M', 'G', 'T' (either upper-case or lower-case) or 's'
 for power-of-two kilobytes, megabytes, gigabytes, terabytes or 512 byte
 sectors respectively. The
 .I size
-of the filesystem may never be larger than the size of the partition.
+of the file system may never be larger than the size of the partition.
 If
 .I size
 parameter is not specified, it will default to the size of the partition.
@@ -59,7 +59,7 @@ parameter is not specified, it will default to the size of the partition.
 The
 .B resize2fs
 program does not manipulate the size of partitions.  If you wish to enlarge
-a filesystem, you must make sure you can expand the size of the
+a file system, you must make sure you can expand the size of the
 underlying partition first.  This can be done using
 .BR fdisk (8)
 by deleting the partition and recreating it with a larger size or using
@@ -69,19 +69,19 @@ if you're using the logical volume manager
 When
 recreating the partition, make sure you create it with the same starting
 disk cylinder as before!  Otherwise, the resize operation will
-certainly not work, and you may lose your entire filesystem.
+certainly not work, and you may lose your entire file system.
 After running
 .BR fdisk (8),
-run resize2fs to resize the ext2 filesystem
+run resize2fs to resize the ext2 file system
 to use all of the space in the newly enlarged partition.
 .PP
 If you wish to shrink an ext2 partition, first use
 .B resize2fs
-to shrink the size of filesystem.  Then you may use
+to shrink the size of file system.  Then you may use
 .BR fdisk (8)
 to shrink the size of the partition.  When shrinking the size of
 the partition, make sure you do not make it smaller than the new size
-of the ext2 filesystem!
+of the ext2 file system!
 .PP
 The
 .B \-b
@@ -90,7 +90,7 @@ and
 options enable and disable the 64bit feature, respectively.  The resize2fs
 program will, of course, take care of resizing the block group descriptors
 and moving other data blocks out of the way, as needed.  It is not possible
-to resize the filesystem concurrent with changing the 64bit status.
+to resize the file system concurrent with changing the 64bit status.
 .SH OPTIONS
 .TP
 .B \-b
@@ -112,14 +112,14 @@ from the following list:
 .br
        16      \-\ Print timing information
 .br
-       32      \-\ Debug minimum filesystem size (\-M) calculation
+       32      \-\ Debug minimum file system size (\-M) calculation
 .TP
 .B \-f
-Forces resize2fs to proceed with the filesystem resize operation, overriding
+Forces resize2fs to proceed with the file system resize operation, overriding
 some safety checks which resize2fs normally enforces.
 .TP
 .B \-F
-Flush the filesystem device's buffer caches before beginning.  Only
+Flush the file system device's buffer caches before beginning.  Only
 really useful for doing
 .B resize2fs
 time trials.
@@ -129,10 +129,11 @@ Shrink the file system to minimize its size as much as possible,
 given the files stored in the file system.
 .TP
 .B \-p
-Prints out a percentage completion bars for each
+Print out percentage completion bars for each
 .B resize2fs
-operation during an offline resize, so that the user can keep track
-of what the program is doing.
+phase during an offline (non-trivial) resize operation, so that the user
+can keep track of what the program is doing.  (For very fast resize
+operations, no progress bars may be displayed.)
 .TP
 .B \-P
 Print an estimate of the number of file system blocks in the file system
@@ -148,7 +149,7 @@ Turns off the 64bit feature and frees blocks that are no longer in use.
 The
 .B resize2fs
 program will heuristically determine the RAID stride that was specified
-when the filesystem was created.  This option allows the user to
+when the file system was created.  This option allows the user to
 explicitly specify a RAID stride setting to be used by resize2fs instead.
 .TP
 .BI \-z " undo_file"
@@ -161,8 +162,8 @@ resize2fs-\fIdevice\fR.e2undo in the directory specified via the
 
 WARNING: The undo file cannot be used to recover from a power or system crash.
 .SH KNOWN BUGS
-The minimum size of the filesystem as estimated by resize2fs may be
-incorrect, especially for filesystems with 1k and 2k blocksizes.
+The minimum size of the file system as estimated by resize2fs may be
+incorrect, especially for file systems with 1k and 2k blocksizes.
 .SH AUTHOR
 .B resize2fs
 was written by Theodore Ts'o <tytso@mit.edu>.