| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f |
| From: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
| Date: | Wed, 18 Jun 2014 10:13:23 -0700 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140618120124.GR9508@dastard> |
| References: | <alpine.DEB.2.19.4.1406180224150.4757@xxxxxxxxxxxxxx> <20140618120124.GR9508@dastard> |
| User-agent: | K-9 Mail for Android |
On June 18, 2014 5:01:24 AM PDT, Dave Chinner <david@xxxxxxxxxxxxx> 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? Christian. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: require 64-bit sector_t, Christoph Hellwig |
|---|---|
| Next by Date: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Dave Chinner |
| Previous by Thread: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Dave Chinner |
| Next by Thread: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |