This is the mail archive of the
cluster-cvs@sourceware.org
mailing list for the cluster.
cluster: RHEL5 - Fix more man page references to gfs2_fsck
- From: Bob Peterson <rpeterso at fedoraproject dot org>
- To: cluster-cvs-relay at redhat dot com
- Date: Fri, 24 Jul 2009 15:03:24 +0000 (UTC)
- Subject: cluster: RHEL5 - Fix more man page references to gfs2_fsck
Gitweb: http://git.fedorahosted.org/git/cluster.git?p=cluster.git;a=commitdiff;h=470a0f93bc2071a1ef26177b854cd7279730c247
Commit: 470a0f93bc2071a1ef26177b854cd7279730c247
Parent: 95c604973535fe61ed27b73e6f0bd098c6d3cd9c
Author: Bob Peterson <rpeterso@redhat.com>
AuthorDate: Fri Jul 24 09:16:19 2009 -0500
Committer: Bob Peterson <rpeterso@redhat.com>
CommitterDate: Fri Jul 24 09:16:19 2009 -0500
Fix more man page references to gfs2_fsck
bz 477072
---
gfs2/man/gfs2_edit.8 | 4 ++--
gfs2/man/gfs2_grow.8 | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/gfs2/man/gfs2_edit.8 b/gfs2/man/gfs2_edit.8
index a14f2b4..d133956 100644
--- a/gfs2/man/gfs2_edit.8
+++ b/gfs2/man/gfs2_edit.8
@@ -86,7 +86,7 @@ Valid block allocation types are: 0 (Free block), 1 (Data block),
2 (Unlinked block), and 3 (Metadata block). If a value from 0 to 3 is
specified, the resource group bitmap will be changed to the new value.
This may be used, for example, to artificially free or allocate a block
-in order to test gfs2_fsck's ability to detect and fix the problem.
+in order to test fsck.gfs2's ability to detect and fix the problem.
Optionally, you may specify the keyword \fIblockbits\fR. This option
will locate and print the block containing the bitmap corresponding to
@@ -120,7 +120,7 @@ and resource groups are allowed. If no value is specified after the
field, the value of the field will be printed to stdout. If a value
is specified, the field's value will be changed. This may be used,
for example, to artificially change the di_size field for an inode
-in order to test gfs2_fsck's ability to detect and fix the problem.
+in order to test fsck.gfs2's ability to detect and fix the problem.
.TP
\fB-s\fs [\fIstructure\fR | \fIblock\fR]
diff --git a/gfs2/man/gfs2_grow.8 b/gfs2/man/gfs2_grow.8
index 30e9e30..4f2ee36 100644
--- a/gfs2/man/gfs2_grow.8
+++ b/gfs2/man/gfs2_grow.8
@@ -37,7 +37,7 @@ You can run gfs2_grow with the \fB-T\fP flag to get a display
of the current state of a mounted GFS2 filesystem.
The gfs2_grow tool uses the resource group (RG) size that was originally
-calculated when mkfs.gfs2 was done. This allows tools like gfs2_fsck
+calculated when mkfs.gfs2 was done. This allows tools like fsck.gfs2
to better ensure the integrity of the file system. Since the new free
space often does not lie on even boundaries based on that RG size,
there may be some unused space on the device after gfs2_grow is run.