Hi Andrew, Thank for your suggestions. I will sort out a document for ocfs2 online file check feature.
Thanks Gang >>> > On Wed, 24 Jun 2015 13:24:17 +0800 Gang He <g...@suse.com> wrote: > >> When there are errors in the ocfs2 filesystem, >> they are usually accompanied by the inode number which caused the error. >> This inode number would be the input to fixing the file. >> One of these options could be considered: >> A file in the sys filesytem which would accept inode numbers. >> This could be used to communication back what has to be fixed or is fixed. >> You could write: >> $# echo "CHECK <inode>" > /sys/fs/ocfs2/devname/filecheck >> or >> $# echo "FIX <inode>" > /sys/fs/ocfs2/devname/filecheck > > This is a userspace feature so it should have user documentation. > Documentation/filesystems/ocfs2.txt is presumably the appropriate > place. > > And the availability of the complete user documentation will make the > review of this patchset more productive. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
