Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752469AbYJSBsx (ORCPT ); Sat, 18 Oct 2008 21:48:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752060AbYJSBsp (ORCPT ); Sat, 18 Oct 2008 21:48:45 -0400 Received: from ipmail05.adl2.internode.on.net ([203.16.214.145]:33366 "EHLO ipmail05.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752055AbYJSBso (ORCPT ); Sat, 18 Oct 2008 21:48:44 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmEDACYv+kh5LF1jiGdsb2JhbACTbQEBARUirGODbA X-IronPort-AV: E=Sophos;i="4.33,441,1220193000"; d="scan'208";a="233925834" Date: Sun, 19 Oct 2008 12:48:30 +1100 From: Dave Chinner To: Martin Michlmayr Cc: Eric Sandeen , Tobias Frost , linux-kernel@vger.kernel.org, debian-arm@lists.debian.org, xfs@oss.sgi.com Subject: Re: XFS filesystem corruption on the arm(el) architecture Message-ID: <20081019014830.GI31761@disturbed> Mail-Followup-To: Martin Michlmayr , Eric Sandeen , Tobias Frost , linux-kernel@vger.kernel.org, debian-arm@lists.debian.org, xfs@oss.sgi.com References: <1222893502.5020.40.camel@moria> <20081002004556.GB30001@disturbed> <48E4213E.9090508@sandeen.net> <20081016212500.GA27228@deprecation.cyrius.com> <48F7BC9F.4080909@sandeen.net> <20081017070109.GA30726@deprecation.cyrius.com> <48F89E0F.6030307@sandeen.net> <20081018085752.GS25834@deprecation.cyrius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081018085752.GS25834@deprecation.cyrius.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1802 Lines: 44 On Sat, Oct 18, 2008 at 10:57:56AM +0200, Martin Michlmayr wrote: > * Eric Sandeen [2008-10-17 09:15]: > > If you unmount & remount, does the ls work then? > > I cannot even mount it: > > debian:~# mkfs.xfs -f /dev/sda5 > meta-data=/dev/sda5 isize=256 agcount=4, agsize=94380 blks > = sectsz=512 attr=2 > data = bsize=4096 blocks=377519, imaxpct=25 > = sunit=0 swidth=0 blks > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=2560, version=2 > = sectsz=512 sunit=0 blks, lazy-count=0 > realtime =none extsz=4096 blocks=0, rtextents=0 > debian:~# mount /dev/sda5 /mnt > [42949596.920000] XFS mounting filesystem sda5 > debian:~# cp /usr/bin/* /mnt/ > debian:~# umount /mnt > debian:~# mount -t xfs /dev/sda5 /mnt > [42949612.290000] XFS mounting filesystem sda5 > [42949612.460000] Starting XFS recovery on filesystem: sda5 (logdev: internal) > [42949612.480000] XFS: xlog_recover_process_data: bad flag > [42949612.500000] XFS: log mount/recovery failed: error 5 > [42949612.500000] XFS: log mount failed > mount: /dev/sda5: can't read superblock > debian:~# That's the log replay indicating that there's a bad transaction header in the log. Very strange - it shoul dbe a clean log. What does xfs_logprint -t /dev/sda5 tell you about the transactions in the log? Cheers, Dave. -- Dave Chinner david@fromorbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/