100 lines · plain
1.. SPDX-License-Identifier: GPL-2.02 3=====================================4OCFS2 file system - online file check5=====================================6 7This document will describe OCFS2 online file check feature.8 9Introduction10============11OCFS2 is often used in high-availability systems. However, OCFS2 usually12converts the filesystem to read-only when encounters an error. This may not be13necessary, since turning the filesystem read-only would affect other running14processes as well, decreasing availability.15Then, a mount option (errors=continue) is introduced, which would return the16-EIO errno to the calling process and terminate further processing so that the17filesystem is not corrupted further. The filesystem is not converted to18read-only, and the problematic file's inode number is reported in the kernel19log. The user can try to check/fix this file via online filecheck feature.20 21Scope22=====23This effort is to check/fix small issues which may hinder day-to-day operations24of a cluster filesystem by turning the filesystem read-only. The scope of25checking/fixing is at the file level, initially for regular files and eventually26to all files (including system files) of the filesystem.27 28In case of directory to file links is incorrect, the directory inode is29reported as erroneous.30 31This feature is not suited for extravagant checks which involve dependency of32other components of the filesystem, such as but not limited to, checking if the33bits for file blocks in the allocation has been set. In case of such an error,34the offline fsck should/would be recommended.35 36Finally, such an operation/feature should not be automated lest the filesystem37may end up with more damage than before the repair attempt. So, this has to38be performed using user interaction and consent.39 40User interface41==============42When there are errors in the OCFS2 filesystem, they are usually accompanied43by the inode number which caused the error. This inode number would be the44input to check/fix the file.45 46There is a sysfs directory for each OCFS2 file system mounting::47 48 /sys/fs/ocfs2/<devname>/filecheck49 50Here, <devname> indicates the name of OCFS2 volume device which has been already51mounted. The file above would accept inode numbers. This could be used to52communicate with kernel space, tell which file(inode number) will be checked or53fixed. Currently, three operations are supported, which includes checking54inode, fixing inode and setting the size of result record history.55 561. If you want to know what error exactly happened to <inode> before fixing, do::57 58 # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/check59 # cat /sys/fs/ocfs2/<devname>/filecheck/check60 61The output is like this::62 63 INO DONE ERROR64 39502 1 GENERATION65 66 <INO> lists the inode numbers.67 <DONE> indicates whether the operation has been finished.68 <ERROR> says what kind of errors was found. For the detailed error numbers,69 please refer to the file linux/fs/ocfs2/filecheck.h.70 712. If you determine to fix this inode, do::72 73 # echo "<inode>" > /sys/fs/ocfs2/<devname>/filecheck/fix74 # cat /sys/fs/ocfs2/<devname>/filecheck/fix75 76The output is like this:::77 78 INO DONE ERROR79 39502 1 SUCCESS80 81This time, the <ERROR> column indicates whether this fix is successful or not.82 833. The record cache is used to store the history of check/fix results. It's84default size is 10, and can be adjust between the range of 10 ~ 100. You can85adjust the size like this::86 87 # echo "<size>" > /sys/fs/ocfs2/<devname>/filecheck/set88 89Fixing stuff90============91On receiving the inode, the filesystem would read the inode and the92file metadata. In case of errors, the filesystem would fix the errors93and report the problems it fixed in the kernel log. As a precautionary measure,94the inode must first be checked for errors before performing a final fix.95 96The inode and the result history will be maintained temporarily in a97small linked list buffer which would contain the last (N) inodes98fixed/checked, the detailed errors which were fixed/checked are printed in the99kernel log.100