On Fri, May 26, 2006 at 12:29:51PM -0500, Eric Sandeen wrote:
> any errors out of the newer mkfs? Can you divide & conquer a bit to see
> when it stopped working? What does the first 512 bytes of /dev/ad0s4 look
> like with the new code; maybe diff that hexdump against one from 2.6.25?
> What does the kernel say when you try to mount it? Not sure what should
> have broken any of this...
>
> -Eric
mkfs.xfs does not report any errors. I think it is
an endian problem as Nathan mentioned.
I am attaching two hexdumps one from xfsprogs-2.6.25 (good),
and the other from xfsprogs-2.7.11 (bad).
On Sat, May 27, 2006 at 05:25:34AM +1000, Nathan Scott wrote:
> Russell mentioned there was an endianness issue in the current
> Freebsd specific headers (iirc) - I don't have a patch though;
> this is probably a symptom of that.
Which headers should I be looking at?
--
Craig Rodrigues
rodrigc@xxxxxxxxxxxxxx
xfsprogs2.6.25_good.txt
Description: Text document
xfsprogs.2.7.11_bad.txt
Description: Text document
|