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