1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377
|
Description: Fix spelling errors reported by lintian
Author: Valentin Vidic <Valentin.Vidic@CARNet.hr>
Last-Update: 2018-01-24
--- a/libocfs2/ocfs2_err.et
+++ b/libocfs2/ocfs2_err.et
@@ -112,7 +112,7 @@
"Bit does not exist in bitmap range"
ec OCFS2_ET_INTERNAL_FAILURE,
- "Internal logic faliure"
+ "Internal logic failure"
ec OCFS2_ET_BAD_GROUP_DESC_MAGIC,
"Bad magic number in group descriptor"
--- a/fsck.ocfs2/fsck.c
+++ b/fsck.ocfs2/fsck.c
@@ -226,7 +226,7 @@
ret = o2fsck_state_init(fs, ost);
if (ret) {
- com_err(whoami, ret, "while intializing o2fsck_state.");
+ com_err(whoami, ret, "while initializing o2fsck_state.");
return ret;
}
--- a/fsck.ocfs2/extent.c
+++ b/fsck.ocfs2/extent.c
@@ -300,7 +300,7 @@
"this record from the extent list?", i, owner)) {
if (!trust_next_free) {
- printf("Can't remove the record becuase "
+ printf("Can't remove the record because "
"next_free_rec hasn't been fixed\n");
continue;
}
--- a/fsck.ocfs2/pass0.c
+++ b/fsck.ocfs2/pass0.c
@@ -177,7 +177,7 @@
if ((bg->bg_list.l_count >
ocfs2_extent_recs_per_gd(ost->ost_fs->fs_blocksize)) &&
prompt(ost, PY, PR_DISCONTIG_BG_COUNT,
- "Discontigous group descriptor at block %"PRIu64" has "
+ "Discontiguous group descriptor at block %"PRIu64" has "
"an extent count of %u, but discontiguous groups can "
"only hold %u records. Set it to %u?", blkno,
bg->bg_list.l_count,
@@ -1019,7 +1019,7 @@
(uint64_t)di->i_blkno)) {
if (!trust_next_free) {
- printf("Can't remove the chain becuase "
+ printf("Can't remove the chain because "
"next_free_rec hasn't been fixed\n");
continue;
}
--- a/fsck.ocfs2/refcount.c
+++ b/fsck.ocfs2/refcount.c
@@ -124,7 +124,7 @@
"this record from the refcount list?",
i, rb_blkno, root_blkno)) {
if (!trust_used) {
- printf("Can't remove the record becuase "
+ printf("Can't remove the record because "
"rl_used hasn't been fixed\n");
continue;
}
@@ -139,7 +139,7 @@
"this record from the refcount list?",
i, rb_blkno, root_blkno)) {
if (!trust_used) {
- printf("Can't remove the record becuase "
+ printf("Can't remove the record because "
"rl_used hasn't been fixed\n");
continue;
}
--- a/fsck.ocfs2/pass2.c
+++ b/fsck.ocfs2/pass2.c
@@ -613,7 +613,7 @@
if (was_set) {
printf("Directory inode %"PRIu64" contains a duplicate "
- "occurance " "of the file name '%.*s' but fsck was "
+ "occurrence " "of the file name '%.*s' but fsck was "
"unable to come up with a unique name so this duplicate "
"name will not be dealt with.\n.",
dbe->e_ino, dirent->name_len, dirent->name);
@@ -621,7 +621,7 @@
}
if (!prompt(ost, PY, PR_DIRENT_DUPLICATE,
- "Directory inode %"PRIu64" contains a duplicate occurance "
+ "Directory inode %"PRIu64" contains a duplicate occurrence "
"of the file name '%.*s'. Replace this duplicate name "
"with '%s'?", dbe->e_ino, dirent->name_len, dirent->name,
new_name)) {
--- a/mounted.ocfs2/mounted.c
+++ b/mounted.ocfs2/mounted.c
@@ -569,7 +569,7 @@
ret = build_partition_list(&dev_list, device);
if (ret) {
- com_err(progname, ret, "while building partiton list");
+ com_err(progname, ret, "while building partition list");
goto bail;
}
--- a/tunefs.ocfs2/feature_indexed_dirs.c
+++ b/tunefs.ocfs2/feature_indexed_dirs.c
@@ -62,7 +62,7 @@
ret = ocfs2_dx_dir_truncate(fs, di->i_blkno);
if (ret) {
ret = TUNEFS_ET_DX_DIRS_TRUNCATE_FAILED;
- tcom_err(ret, "while rebulid indexed tree");
+ tcom_err(ret, "while rebuild indexed tree");
}
}
--- a/tunefs.ocfs2/feature_quota.c
+++ b/tunefs.ocfs2/feature_quota.c
@@ -108,7 +108,7 @@
ret = ocfs2_init_global_quota_file(fs, type);
if (ret) {
- tcom_err(ret, "while initilizing global %s quota files",
+ tcom_err(ret, "while initializing global %s quota files",
type2name(type));
return ret;
}
@@ -118,7 +118,7 @@
type2name(type));
ret = ocfs2_init_local_quota_files(fs, type);
if (ret) {
- tcom_err(ret, "while initilizing local %s quota files",
+ tcom_err(ret, "while initializing local %s quota files",
type2name(type));
return ret;
}
--- a/o2info/o2info.1.in
+++ b/o2info/o2info.1.in
@@ -7,9 +7,9 @@
.SH "DESCRIPTION"
.PP
\fBo2info\fR shows information about \fIOCFS2\fR file systems. It differs from \fBdebugfs.ocfs2(8)\fR
-in that it allows users with limited read priviledges to query similar information. Users do not have
+in that it allows users with limited read privileges to query similar information. Users do not have
to have the read privilege on the device as is expected by \fBdebugfs.ocfs2(8)\fR. This utility allows
-users to provide a path to an object on a mounted file system. The user needs to have the read priviledge
+users to provide a path to an object on a mounted file system. The user needs to have the read privilege
on that object.
.SH "OPTIONS"
@@ -66,7 +66,7 @@
.SH "EXAMPLES"
.PP
-Non-priviledged users can query the volume information by providing the path to a file on
+Non-privileged users can query the volume information by providing the path to a file on
a mounted file system. Priviledged users can provide the path to the device.
.in +4n
--- a/libocfs2/ocfs2.7.in
+++ b/libocfs2/ocfs2.7.in
@@ -281,7 +281,7 @@
\fBocfs2console(8)\fR has been obsoleted.
\fBo2info(8)\fR is a new utility that can be used to provide file system information.
-It allows non-priviledged users to see the enabled file system features, block and
+It allows non-privileged users to see the enabled file system features, block and
cluster sizes, extended file stat, free space fragmentation, etc.
\fBo2hbmonitor(8)\fR is a \fBo2hb\fR heartbeat monitor. It is an extremely light weight
@@ -289,7 +289,7 @@
warn threshold. This utility is useful in identifying volumes encountering I/O delays.
\fBdebugfs.ocfs2(8)\fR has some new commands. \fInet_stats\fR shows the \fBo2net\fR
-message times between various nodes. This is useful in indentifying nodes are that slowing
+message times between various nodes. This is useful in identifying nodes are that slowing
down the cluster operations. \fIstat_sysdir\fR allows the user to dump the entire system
directory that can be used to debug issues. \fIgrpextents\fR dumps the complete free space
fragmentation in the cluster group allocator.
@@ -517,7 +517,7 @@
Non-clustered volumes do not interact with the cluster stack. One can have both
clustered and non-clustered volumes mounted at the same time.
-While formating a non-clustered volume, users should consider the possibility of later
+While formatting a non-clustered volume, users should consider the possibility of later
converting that volume to a clustered one. If there is a possibility of that, then the
user should add enough node-slots using the -N option. Adding node-slots during format
creates journals with large extents. If created later, then the journals will be
@@ -684,7 +684,7 @@
This is the file system \fIinformation\fR utility. It provides information like the features
enabled on disk, block size, cluster size, free space fragmentation, etc.
-It can be used by both priviledged and non-priviledged users. Users having read permission
+It can be used by both privileged and non-privileged users. Users having read permission
on the device can provide the path to the device. Other users can provide the path to a
file on a mounted file system.
--- a/mkfs.ocfs2/mkfs.ocfs2.8.in
+++ b/mkfs.ocfs2/mkfs.ocfs2.8.in
@@ -145,8 +145,8 @@
.TP
\fBxattr\fR
Enable extended attributes support. With this enabled, users can attach name:value pairs to objects
-within the file system. In \fIOCFS2\fR, the names can be upto 255 bytes in length, terminated by the first
-NUL byte. While it is not required, printable names (ASCII) are recommended. The values can be upto 64KB of
+within the file system. In \fIOCFS2\fR, the names can be up to 255 bytes in length, terminated by the first
+NUL byte. While it is not required, printable names (ASCII) are recommended. The values can be up to 64KB of
arbitrary binary data. Attributes can be attached to all types of inodes: regular files, directories,
symbolic links, device nodes, etc. This feature is required for users wanting to use extended security
facilities like POSIX ACLs or SELinux.
@@ -167,7 +167,7 @@
.TP
\fBindexed-dirs\fR
-Enable directory indexing support. With this feature enabled, the file system creates indexed tree for non-inline directory entries. For large scale directories, directory entry lookup perfromance from the indexed tree is faster then from the legacy directory blocks.
+Enable directory indexing support. With this feature enabled, the file system creates indexed tree for non-inline directory entries. For large scale directories, directory entry lookup performance from the indexed tree is faster then from the legacy directory blocks.
.TP
\fBdiscontig-bg\fR
--- a/tunefs.ocfs2/o2cluster.8.in
+++ b/tunefs.ocfs2/o2cluster.8.in
@@ -20,7 +20,7 @@
If a dirty journal is detected, it implies one of two scenarios. Either the file system is
mounted on another node, or, the last node to have it mounted, crashed. There is no way, short
of joining the cluster, that the utility can use to differentiate between the two. Considering
-this utility is targetted to be used in scenarios when the user is looking to change the
+this utility is targeted to be used in scenarios when the user is looking to change the
on-disk cluster stack, it becomes a chicken-and-egg problem.
If one were to run into this scenario, the user should manually re-confirm that the file system
@@ -35,7 +35,7 @@
The valid stack names are \fBo2cb\fR, \fBpcmk\fR, and \fBcman\fR.
-The cluster name can be upto 16 characters. The \fIo2cb\fR stack further restricts the names to
+The cluster name can be up to 16 characters. The \fIo2cb\fR stack further restricts the names to
contain only alphanumeric characters.
The valid flags for the \fIo2cb\fR stack are \fBlocal\fR and \fBglobal\fR, denoting the two heartbeat
--- a/fsck.ocfs2/fsck.ocfs2.checks.8.in
+++ b/fsck.ocfs2/fsck.ocfs2.checks.8.in
@@ -641,7 +641,7 @@
.SS "REFCOUNT_LOC_INVALID"
Refcount loc can only be valid if the file has refcount flag set. Fsck has
-found that a file has refcount loc while it does't have refcount flag set.
+found that a file has refcount loc while it doesn't have refcount flag set.
Answering yes reset refcount loc to zero for the file.
@@ -718,7 +718,7 @@
.SS "REFCOUNT_BLOCK_INVALID"
Refcount block stores the refcount record for physical clusters of a file.
-It is found refering an invalid refcount block.
+It is found referring an invalid refcount block.
Answering yes remove this refcount block.
@@ -732,7 +732,7 @@
.SS "REFCOUNT_ROOT_BLOCK_INVALID"
Root refcount block is the root of the refcount record for a file. It is found
-refering an invalid refcount block.
+referring an invalid refcount block.
Answering yes remove this refcount block and clear refcount flag from this file.
@@ -749,9 +749,9 @@
Answering yes update the corresponding refcount record.
.SS "REFCOUNT_COUNT"
-Refcount tree contains a record of how many files refering to this tree.
+Refcount tree contains a record of how many files referring to this tree.
A tree was found whose recorded number of files doesn't match the real
-files refering to the tree.
+files referring to the tree.
Answering yes resets the number of files to reflect the real number
of files that were associated with the tree.
--- a/fsck.ocfs2/pass1b.c
+++ b/fsck.ocfs2/pass1b.c
@@ -1082,7 +1082,7 @@
* 3. It has the same tree as others.
* Store refcount_loc if we find one.
*
- * if there is other file that does't have the same tree, set refcount_loc
+ * if there is other file that doesn't have the same tree, set refcount_loc
* to UINT64_MAX and stop the search.
*/
static int find_refcount_func(struct dup_cluster *dc, struct dup_inode *di,
--- a/debugfs.ocfs2/debugfs.ocfs2.8.in
+++ b/debugfs.ocfs2/debugfs.ocfs2.8.in
@@ -48,7 +48,7 @@
.TP
\fB\-s, \-\-superblock\fR \fIbackup\-number\fR
-\fImkfs.ocfs2\fR makes upto 6 backup copies of the superblock at offsets 1G, 4G,
+\fImkfs.ocfs2\fR makes up to 6 backup copies of the superblock at offsets 1G, 4G,
16G, 64G, 256G and 1T depending on the size of the volume. Use this option to
specify the backup, 1 thru 6, to use to open the volume.
--- a/fsck.ocfs2/fsck.ocfs2.8.in
+++ b/fsck.ocfs2/fsck.ocfs2.8.in
@@ -77,7 +77,7 @@
.TP
\fB\-r\fR \fIbackup-number\fR
-\fImkfs.ocfs2\fR makes upto 6 backup copies of the superblock at offsets
+\fImkfs.ocfs2\fR makes up to 6 backup copies of the superblock at offsets
1G, 4G, 16G, 64G, 256G and 1T depending on the size of the volume.
Use this option to specify the backup, 1 thru 6, to use to recover the
superblock.
--- a/libo2cb/o2cb.7.in
+++ b/libo2cb/o2cb.7.in
@@ -116,7 +116,7 @@
It is for this reason, this mode is recommended for users that have 3 or more OCFS2
mounts.
-O2CB allows upto \fB32\fR heartbeat regions to be configured in the global heartbeat mode.
+O2CB allows up to \fB32\fR heartbeat regions to be configured in the global heartbeat mode.
.SH "ONLINE CLUSTER MODIFICATION"
.PP
--- a/o2cb_ctl/ocfs2.cluster.conf.5.in
+++ b/o2cb_ctl/ocfs2.cluster.conf.5.in
@@ -18,7 +18,7 @@
in /etc/sysconfig/o2cb [\fBo2cb.sysconfig(5)\fR].
The \fBcluster stanza\fR specifies the name of the cluster, number of nodes and the heartbeat mode.
-The cluster name can include upto 16 alphanumeric characters [0-9A-Za-z]. No special characters
+The cluster name can include up to 16 alphanumeric characters [0-9A-Za-z]. No special characters
are allowed.
.TS
@@ -28,7 +28,7 @@
Parameters Description
node_count Number of nodes in the cluster
heartbeat_mode \fBlocal\fR or \fBglobal\fR heartbeat
-name Cluster name (upto 16 alphanumeric chars [0-9A-Za-z])
+name Cluster name (up to 16 alphanumeric chars [0-9A-Za-z])
.TE
.BR
@@ -54,7 +54,7 @@
.BR
The \fBheartbeat stanza\fR specifies the global heartbeat region UUIDs. A cluster can have
-upto 32 heartbeat regions. This is an optional stanza and is only required if the global
+up to 32 heartbeat regions. This is an optional stanza and is only required if the global
heartbeat mode is enabled. In other words, the regions are only used if \fBheartbeat_mode = global\fR
is in the \fIcluster\fR stanza. If not, this stanza is ignored.
--- a/tunefs.ocfs2/o2cluster.c
+++ b/tunefs.ocfs2/o2cluster.c
@@ -66,7 +66,7 @@
verbosef(VL_OUT, "Valid stack names are \"o2cb\", \"pcmk\" and \"cman\".\n\n");
- verbosef(VL_OUT, "Cluster names can be upto 16 characters. The o2cb stack further restricts\n");
+ verbosef(VL_OUT, "Cluster names can be up to 16 characters. The o2cb stack further restricts\n");
verbosef(VL_OUT, "the names to contain only alphanumeric characters.\n\n");
verbosef(VL_OUT, "For the o2cb stack, valid flags are \"local\" and \"global\" denoting the two\n");
--- a/vendor/common/o2cb.sysconfig.5.in
+++ b/vendor/common/o2cb.sysconfig.5.in
@@ -24,7 +24,7 @@
\fBO2CB_BOOTCLUSTER\fR
Name of the active cluster. While /etc/ocfs2/cluster.conf can hold descriptions of
multiple clusters, only one can be active at any one time. The name of that
-active cluster is specified here. The name itself can be upto 16 alphanumeric
+active cluster is specified here. The name itself can be up to 16 alphanumeric
characters [0-9A-Za-z] with no special characters.
.PP
|