From: Eric Sandeen <sandeen@sandeen.net>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: xfs@oss.sgi.com
Subject: Re: Volume fine on x86_64, corruption on ARM
Date: Mon, 28 Jan 2013 16:37:25 -0600 [thread overview]
Message-ID: <5106FDA5.80409@sandeen.net> (raw)
In-Reply-To: <20130127225258.GA2287@vicerveza.homeunix.net>
On 1/27/13 4:52 PM, Lluís Batlle i Rossell wrote:
> Hello,
>
> I'm using linux 3.7.3 in both machines (x86_64 and armv5tel), and I created
> a volume in x86_64 to be the rootfs for the ARM. All fine, until I plugged it
> into the ARM (Log below).
>
> Given the corruption, I used xfs_repair in the x86_64, moved a lot of files into lost+found, plugged it back to the ARM, booted, and corruption again.
>
> In the same USB HD, in the same ARM, and this same way, I've used succesfully
> ext4 and btrfs for a long time. Is there any known issue with ARM?
>
> Thank you,
> Lluís.
>
> ----------------------
> starting systemd...
> systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ)
>
> Welcome to NixOS 0.2pre-4eb2b09-af495e0!
>
> Failed to insert module 'autofs4'
> dea96000: 58 46 53 42 00 00 10 00 00 00 00 00 01 bd 26 f0 XFSB..........&.
> XFS (sda1): Internal error xfs_da_do_buf(2) at line 2192 of file fs/xfs/xfs_da_btree.c. Caller 0xbf057e68
So this was trying to read a dir2 directory metadata leaf block, and it didn't find the right magic.
XFSB is superblock magic . . .
I tested an image which (I think) contains every dir2 format, created on x86_64
(under a RHEL6 3.2 kernel) and checked it on ARM (a raspberry pi 3.2.24 kernel)
so it's not really quite an apples to apples test.
Does the filesystem check clean on x86_64 right after you create it? How did you
create it?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-01-28 22:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 22:52 Volume fine on x86_64, corruption on ARM Lluís Batlle i Rossell
2013-01-28 1:52 ` Eric Sandeen
2013-01-28 8:03 ` Lluís Batlle i Rossell
2013-01-28 10:46 ` Stan Hoeppner
2013-01-28 13:37 ` Lluís Batlle i Rossell
2013-01-28 17:10 ` Eric Sandeen
2013-01-28 22:37 ` Eric Sandeen [this message]
2013-01-28 22:40 ` Lluís Batlle i Rossell
2013-01-28 22:45 ` Eric Sandeen
2013-01-28 22:50 ` Lluís Batlle i Rossell
2013-01-29 5:21 ` Stan Hoeppner
2013-01-31 20:19 ` Phillip Lougher
2013-02-03 22:46 ` Brian Foster
2013-02-04 17:46 ` Lluís Batlle i Rossell
2013-02-27 14:51 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2014-02-15 3:18 Bill Webster
2014-02-16 22:21 ` Dave Chinner
2014-02-17 1:53 ` Stan Hoeppner
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=5106FDA5.80409@sandeen.net \
--to=sandeen@sandeen.net \
--cc=viric@viric.name \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.