@@ -5,12 +5,12 @@ This document will describe OCFS2 online file check feature.
5
5
6
6
Introduction
7
7
============
8
- OCFS2 is often used in high-availaibility systems. However, OCFS2 usually
8
+ OCFS2 is often used in high-availability systems. However, OCFS2 usually
9
9
converts the filesystem to read-only when encounters an error. This may not be
10
10
necessary, since turning the filesystem read-only would affect other running
11
11
processes as well, decreasing availability.
12
12
Then, a mount option (errors=continue) is introduced, which would return the
13
- -EIO errno to the calling process and terminate furhter processing so that the
13
+ -EIO errno to the calling process and terminate further processing so that the
14
14
filesystem is not corrupted further. The filesystem is not converted to
15
15
read-only, and the problematic file's inode number is reported in the kernel
16
16
log. The user can try to check/fix this file via online filecheck feature.
@@ -44,7 +44,7 @@ There is a sysfs directory for each OCFS2 file system mounting:
44
44
45
45
/sys/fs/ocfs2/<devname>/filecheck
46
46
47
- Here, <devname> indicates the name of OCFS2 volumn device which has been already
47
+ Here, <devname> indicates the name of OCFS2 volume device which has been already
48
48
mounted. The file above would accept inode numbers. This could be used to
49
49
communicate with kernel space, tell which file(inode number) will be checked or
50
50
fixed. Currently, three operations are supported, which includes checking
@@ -76,14 +76,14 @@ The output is like this:
76
76
This time, the <ERROR> column indicates whether this fix is successful or not.
77
77
78
78
3. The record cache is used to store the history of check/fix results. It's
79
- defalut size is 10, and can be adjust between the range of 10 ~ 100. You can
79
+ default size is 10, and can be adjust between the range of 10 ~ 100. You can
80
80
adjust the size like this:
81
81
82
82
# echo "<size>" > /sys/fs/ocfs2/<devname>/filecheck/set
83
83
84
84
Fixing stuff
85
85
============
86
- On receivng the inode, the filesystem would read the inode and the
86
+ On receiving the inode, the filesystem would read the inode and the
87
87
file metadata. In case of errors, the filesystem would fix the errors
88
88
and report the problems it fixed in the kernel log. As a precautionary measure,
89
89
the inode must first be checked for errors before performing a final fix.
0 commit comments