[Top] [All Lists]

Architecture specific headers

To: linux-xfs@xxxxxxxxxxx
Subject: Architecture specific headers
From: KrishnaPradeep Tamma <krishnapradeep@xxxxxxxxx>
Date: Thu, 14 Apr 2005 13:50:06 -0500
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Jtgs7sBtpV4nahgeZ05QlfiQzn2p2ZlaoRmzwHWt3CPKA8UxVBad9CUSaDjrorm6B7aQY1R5EXgJ3llqCdXHo+dCmteiM97g/wDqWWKR7lBvCVAyIjAYaBiZkl6AMo66wJu3PXbgmOBTg5gPkxN4nkGGj6CRFVpaUO40jqjU4a8=
Reply-to: KrishnaPradeep Tamma <krishnapradeep@xxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
We are experimenting with XFS on Linux X86. We found that super block
has endian problems and need to use xsf_xlatesb to convert to X86.

Now we got similar problem with log header. We tried to read the first
log block and match with XLOG_HEADER_MAGIC_NUM. But we are getting a
different number.

Does the log structure also need some endian conversion?

Could some tell which function should we use to convert the same?


<Prev in Thread] Current Thread [Next in Thread>