From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 415407F3F for ; Wed, 18 Jun 2014 18:07:42 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id E37D0AC003 for ; Wed, 18 Jun 2014 16:07:38 -0700 (PDT) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by cuda.sgi.com with ESMTP id ZFoE9KX95NYn06OF for ; Wed, 18 Jun 2014 16:07:36 -0700 (PDT) Date: Thu, 19 Jun 2014 09:07:21 +1000 From: Dave Chinner Subject: Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f Message-ID: <20140618230721.GD4453@dastard> References: <20140618120124.GR9508@dastard> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Christian Kujau Cc: xfs@oss.sgi.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 > 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