From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: Volume fine on x86_64, corruption on ARM
Date: Mon, 28 Jan 2013 23:50:10 +0100 [thread overview]
Message-ID: <20130128225010.GL2287@vicerveza.homeunix.net> (raw)
In-Reply-To: <5106FF76.6080102@sandeen.net>
On Mon, Jan 28, 2013 at 04:45:10PM -0600, Eric Sandeen wrote:
> On 1/28/13 4:40 PM, Lluís Batlle i Rossell wrote:
> > On Mon, Jan 28, 2013 at 04:37:25PM -0600, Eric Sandeen wrote:
> >> 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?
> > I run:
> > mkfs.xfs /dev/sdb1
> >
> > Then I copied files to it.
>
> On the x86_64 machine, right. Just to be sure, can you do an xfs_repair
> on x86_64 to be sure it's clean at this point?
I don't have the fs anymore... I have that disk in use right now (with ext4
finally).
But I didn't try to run an xfs_repair straight after writing the files with
x86_64.
> > After the first crash in the arm, I used xfs_repair on the
> > x86_64. It created many lost+found.
>
> capturing the repair output here would be helpful.
ouhm I can't find it now. Sorry.
> > Then I tried again in the ARM, and it
> > crashed again the same way.
>
> And by "tried again" do you mean you booted from that filesystem on
> the arm box, I guess, and then encountered the corruption?
Yes, the same procedure I used in the first case.
In the next days I'll try to get some quick test over a loop device or so, and
see if I can reproduce it.
Thank you,
Lluís.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-01-28 22:50 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
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 [this message]
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=20130128225010.GL2287@vicerveza.homeunix.net \
--to=viric@viric.name \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox