Thanks Dave and Eric for your kind support.<br>We will then see if it is worth putting in effort for these changes or not.<br><br>Thanks <br><br><br><br><br><div class="gmail_quote">On Mon, Nov 30, 2009 at 12:13 PM, Dave Chinner <span dir="ltr"><<a href="mailto:david@fromorbit.com">david@fromorbit.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Mon, Nov 30, 2009 at 10:47:41AM +0530, Nitin Arora wrote:<br>
> The problem is that big endian machine cannot recognize the<br>
> journal which was written in little endian format by the little<br>
> endian machine and once the journal is zerod out it can be<br>
> mouted.<br>
><br>
> Now the solution to above problem seems writing journal always in<br>
> big endian format.<br>
<br>
</div>Or you could just replay the log on the little endian machine and do<br>
a clean unmount, then you should be able to move it to the big<br>
endian machine without losing anything.<br>
<div class="im"><br>
> Please suggest me, Is there any design limitation in XFS for this.<br>
<br>
</div>No design limitation, just a *lot* of work to change. If you don't<br>
have a few months handy to work on this, I'd just use the above<br>
method....<br>
<div class="im"><br>
> Is it okay and feasible to implement it if yes then please give<br>
> some pointers so that it can be implemented,<br>
<br>
</div>All log headers, tails and sector fills need to be converted, every log<br>
item format routine needs a big-endian version, log recovery needs<br>
to be able to read both host-format and big-endian logs, all the<br>
userspace tools need to learn about different log formats, QA tests<br>
need to be written, etc.<br>
<div class="im"><br>
> under some suitable<br>
> compile time switch.<br>
<br>
</div>It could be done with a superblock feature bit, so the same kernel<br>
could support both big-endian logs and host format.<br>
<br>
Cheers,<br>
<br>
Dave.<br>
<font color="#888888">--<br>
Dave Chinner<br>
<a href="mailto:david@fromorbit.com">david@fromorbit.com</a><br>
</font></blockquote></div><br>