From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: xfs@oss.sgi.com
Subject: Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f
Date: Thu, 19 Jun 2014 09:07:21 +1000 [thread overview]
Message-ID: <20140618230721.GD4453@dastard> (raw)
In-Reply-To: <e2537966-9b06-45eb-b2c7-dd5cffa968dd@email.android.com>
On Wed, Jun 18, 2014 at 10:13:23AM -0700, Christian Kujau wrote:
>
>
> On June 18, 2014 5:01:24 AM PDT, Dave Chinner
> <david@fromorbit.com> wrote:
> >Yes, that's the only way to safely move a filesystem between
> >machines of different endianness - a clean log has nothing to
> >replay, so no endian problems and all new records will be written
> >according to the endianness of the host the filesystem is
> >currently mounted on.
>
> OK, thanks for explaining that.
>
> When the PowerPC box crashed there should not have been any i/o on
> the file system - so, if there was nothing to commit, clearing the
> log with "xfs_repair -L" should not lose any data, right?
In theory. use xfs_logprint to check the log is empty...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-06-18 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 9:44 log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f Christian Kujau
2014-06-18 12:01 ` Dave Chinner
2014-06-18 17:13 ` Christian Kujau
2014-06-18 23:07 ` Dave Chinner [this message]
[not found] ` <alpine.DEB.2.19.4.1406181719040.4757@trent.utfs.org>
2014-09-24 19:14 ` Christian Kujau
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=20140618230721.GD4453@dastard \
--to=david@fromorbit.com \
--cc=lists@nerdbynature.de \
--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