<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace;font-size:small">Hi Lars,<br><br></div><div class="gmail_default" style="font-family:courier new,monospace;font-size:small">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. <br>
<br>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.<br><br></div><div class="gmail_default" style="font-family:courier new,monospace;font-size:small">
Thanks,<br><br></div><div class="gmail_default" style="font-family:courier new,monospace;font-size:small">Vineeth<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 17, 2013 at 10:06 AM, Lars Marowsky-Bree <span dir="ltr"><<a href="mailto:lmb@suse.com" target="_blank">lmb@suse.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 2013-05-17T09:51:19, Vineeth Thampi <<a href="mailto:vineeth.thampi@gmail.com">vineeth.thampi@gmail.com</a>> wrote:<br>
<br>
> Has anybody tried to modify o2quo_fence_self() so that the node does not<br>
> restart, but make the all the OCFS2 filesystem mounts readonly?<br>
<br>
</div>You can't get a consistent RO view of the file system if you're no<br>
longer quorate.<br>
<br>
<br>
Regards,<br>
Lars<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Architect Storage/HA<br>
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)<br>
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde<br>
<br>
</font></span></blockquote></div><br></div>