thanks for quick response, so does this mean, we can even remove that option on current 1.4 OCFS2 and prepare new host also without this option and we swing the storage and we should be fine?<div><br></div><div>Regards,<br>
Pravin<br><div><br><div class="gmail_quote">On Tue, Oct 30, 2012 at 12:03 PM, Herbert van den Bergh <span dir="ltr"><<a href="mailto:herbert.van.den.bergh@oracle.com" target="_blank">herbert.van.den.bergh@oracle.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
The datavolume option didn't really do much. It just changed the
filesystem identifier from OCFS2 to OCFS V1, so some programs which
shall not be named would detect it as OCFS and do something
special. Those programs have long since been fixed. And there's
absolutely no other functional behavior change with or without the
parameter.<br>
<br>
Thanks,<br>
Herbert.<div><div class="h5"><br>
<br>
<div>On 10/30/12 8:08 AM, Pravin K Patil
wrote:<br>
</div>
<blockquote type="cite">Hi All,
<div><br>
</div>
<div>While building new servers, we just noticed that on new
servers which are SLES11 SP2 and OCFS2 1.6 there is no option
for mount as datavolume</div>
<div>All our file system which have oracle data files are mounted
with this option in current system which is SLES10 SP4 and OCFS
1.4</div>
<div><br>
</div>
<div>So when we swing the storage, we will have to be careful of
this mount option. Any suggestions?</div>
<div><br>
</div>
<div>Regards,<br>
Pravin<br>
<br>
<div class="gmail_quote">On Thu, Oct 25, 2012 at 10:54 PM,
Pravin K Patil <span dir="ltr"><<a href="mailto:pravinkpatil@gmail.com" target="_blank">pravinkpatil@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks a
lot for all the responses, I will reply back with practical
experience in few weeks.<span><font color="#888888">
<div>
<br>
</div>
</font></span>
<div><span><font color="#888888">Pravin</font></span>
<div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Oct 25, 2012 at 9:39
PM, Tiger Yang <span dir="ltr"><<a href="mailto:tiger.yang@oracle.com" target="_blank">tiger.yang@oracle.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#ffffff" text="#000000"> 1.6 could
recoginze 1.4 format, but after moving to the
new server, maybe need enable new features
which only supported by 1.6 via tunefs.ocfs2.<br>
<br>
Thanks,<br>
Tiger
<div>
<div><br>
<br>
On 10/26/2012 01:19 AM, Pravin K Patil
wrote: </div>
</div>
<blockquote type="cite">
<div>
<div>Hi,
<div><br>
</div>
<div>We have current Oracle RAC running
with OCFS2 1.4.2 on SLES10 SP4 servers.</div>
<div>we are building new RAC nodes with
SLES11 SP2 which will have OCFS2 1.6</div>
<div><br>
</div>
<div>We plan to just represent the storage
from current HW to new HW and expect the
new server to recognize all FS and let
Oracle start RAC instances.</div>
<div><br>
</div>
<div>Are there any steps required
after/before presenting the storage to
new server.</div>
<div><br>
</div>
<div>Regards,<br>
Pravin</div>
</div>
</div>
<pre><fieldset></fieldset>
_______________________________________________
Ocfs2-users mailing list
<a href="mailto:Ocfs2-users@oss.oracle.com" target="_blank">Ocfs2-users@oss.oracle.com</a>
<a href="https://oss.oracle.com/mailman/listinfo/ocfs2-users" target="_blank">https://oss.oracle.com/mailman/listinfo/ocfs2-users</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Ocfs2-users mailing list
<a href="mailto:Ocfs2-users@oss.oracle.com" target="_blank">Ocfs2-users@oss.oracle.com</a>
<a href="https://oss.oracle.com/mailman/listinfo/ocfs2-users" target="_blank">https://oss.oracle.com/mailman/listinfo/ocfs2-users</a></pre>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div></div>