| To: | Christian Kujau <lists@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 19 Jun 2014 09:07:21 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <e2537966-9b06-45eb-b2c7-dd5cffa968dd@xxxxxxxxxxxxxxxxx> |
| References: | <alpine.DEB.2.19.4.1406180224150.4757@xxxxxxxxxxxxxx> <20140618120124.GR9508@dastard> <e2537966-9b06-45eb-b2c7-dd5cffa968dd@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@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? In theory. use xfs_logprint to check the log is empty... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Christian Kujau |
|---|---|
| Next by Date: | Re: XFS WARN_ON in xfs_vm_writepage, Dave Chinner |
| Previous by Thread: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Christian Kujau |
| Next by Thread: | xfs_freeze, 陈文东 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |