Hi, On the same topic, I need to set the filesytem as OCFS2_OSB_HARD_RO (Instead of a soft RO) in case I want to have an alternative to restart the node in case of heartbeat failure or network failure?
Thanks, Vineeth On Fri, May 17, 2013 at 10:10 AM, Vineeth Thampi <vineeth.tha...@gmail.com>wrote: > Hi Lars, > > I agree, but then if you make the filesystem RO, you are giving the user > an option to umount the filesystem, may be restart O2CB or take care of the > connectivity issue. > > I just thought of making the FS RO as a mode of telling user that > something has gone wrong, and that the Filesystem wont get corrupted by the > user. > > Thanks, > > Vineeth > > > On Fri, May 17, 2013 at 10:06 AM, Lars Marowsky-Bree <l...@suse.com> wrote: > >> On 2013-05-17T09:51:19, Vineeth Thampi <vineeth.tha...@gmail.com> wrote: >> >> > Has anybody tried to modify o2quo_fence_self() so that the node does not >> > restart, but make the all the OCFS2 filesystem mounts readonly? >> >> You can't get a consistent RO view of the file system if you're no >> longer quorate. >> >> >> Regards, >> Lars >> >> -- >> Architect Storage/HA >> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix >> Imendörffer, HRB 21284 (AG Nürnberg) >> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde >> >> >
_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com https://oss.oracle.com/mailman/listinfo/ocfs2-users
