From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 support which architectures and can the cluster work under mixed architectures?
Date: Sat, 8 Aug 2015 07:44:38 -0500 [thread overview]
Message-ID: <55C5F9B6.3050400@suse.de> (raw)
In-Reply-To: <55C309E0.6040103@huawei.com>
On 08/06/2015 02:16 AM, Joseph Qi wrote:
> On 2015/8/6 13:26, Junxiao Bi wrote:
>> Hi Gang,
>>
>> On 08/06/2015 11:03 AM, Gang He wrote:
>>> Hello guys,
>>>
>>> >From the document(https://oss.oracle.com/projects/ocfs2/), it says that OCFS2 supports x86, x86_64, ia64 and ppc64. I am not sure that this doc is up-to-date, now, OCFS2 supports any other architecture? e.g. s390x?
>>> The second question, since OCFS2 is a cluster FS and support multiple architectures, can a OCFS2 cluster work under a mixed architectures environment? e.g. some nodes are x86, some nodes are ppc64.
>> I think ocfs2 works good on le endian, but maybe not on big endian
>> though i never test it. From the source code, kernel seemed be prepared
>> for big endian, but for tools, maybe not, i found lot of codes reading
>> stuff from disk to memory without conversion in fsck.ocfs2. I am not
>> sure about other tools, so may need do a full check.
>>
> Junxiao is right. Most tools are not taking care the endian conversion.
> They just treat them as little endian which fits x86.
> Maybe we have to do some changes for this.
>
OCFS2 supports big-endian architectures. There has been significant
effort in making sure that it is big-endian compatible.
Though it is capable of running on mixed architectures, we do not
recommend it.
--
Goldwyn
prev parent reply other threads:[~2015-08-08 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 3:03 [Ocfs2-devel] OCFS2 support which architectures and can the cluster work under mixed architectures? Gang He
2015-08-06 5:26 ` Junxiao Bi
2015-08-06 5:49 ` Gang He
2015-08-06 5:55 ` Junxiao Bi
2015-08-06 7:16 ` Joseph Qi
2015-08-08 12:44 ` Goldwyn Rodrigues [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C5F9B6.3050400@suse.de \
--to=rgoldwyn@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox