Hi Goldwyn, On 2015/3/4 2:08, Goldwyn Rodrigues wrote: > OCFS2 is often used in high-availaibility systems. However, ocfs2 > converts the filesystem to read-only at the drop of the hat. This > may not be necessary, since turning the filesystem read-only would > affect other running processes as well, decreasing availability. > > This attempt is to add errors=continue, which would return the EIO > to the calling process and terminate furhter processing so that > the filesystem is not corrupted further. However, the filesystem > is not converted to read-only. > > As a future plan, I intend to create a small utility or extend > fsck.ocfs2 to fix small errors such as in the inode. The input > to the utility such as the inode can come from the kernel logs > so we don't have to schedule a downtime for fixing small-enough > errors. I am interested in your thought. As a cluster filesystem, I don't think it is a good idea that we set the whole filesystem to readonly because of a small error (for example, inode OCFS2_VALID_FL not set). It impacts too much. So we can isolate some errors and fix them in the backgroud, without offline fsck. I think you can send a RFC to discuss this topic.
-- Joseph _______________________________________________ Ocfs2-devel mailing list Ocfs2-devel@oss.oracle.com https://oss.oracle.com/mailman/listinfo/ocfs2-devel
