From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id p17Kr66x068050 for ; Mon, 7 Feb 2011 14:53:06 -0600 Received: from estes.americas.sgi.com (estes.americas.sgi.com [128.162.236.10]) by relay2.corp.sgi.com (Postfix) with ESMTP id 122F230408F for ; Mon, 7 Feb 2011 12:55:37 -0800 (PST) Message-ID: <4D505C48.8050203@sgi.com> Date: Mon, 07 Feb 2011 14:55:36 -0600 From: Bill Kendall MIME-Version: 1.0 Subject: Re: xfsdump SGI_FS_BULKSTAT errno = 22, how could this IRIX bug get into Ubuntu 10.04 Lucid between kernels 2.6.32-27 and 2.6.32-26? References: <4D49A35B.6030009@sgi.com> <20110203045836.GV11040@dastard> <4D4ABEF7.7000400@lueckdatasystems.com> <20110204000823.GW11040@dastard> <4D4C0965.9010905@lueckdatasystems.com> <20110204204927.GZ11040@dastard> In-Reply-To: <20110204204927.GZ11040@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: linux-xfs@oss.sgi.com, Dann Frazier , Michael Lueck On 02/04/2011 02:49 PM, Dave Chinner wrote: > On Fri, Feb 04, 2011 at 09:12:53AM -0500, Michael Lueck wrote: >> Dave Chinner wrote: >>> Ok, so xfsdump i seeing a short bulkstat, then an EINVAL returned >> >from the next bulkstat. That's not a race condition, and makes me >>> think you have some kind of on-disk corruption. >> >> Very odd that some kind of on-disk corruption is suddenly causing >> xfsdump problems starting with Ubuntu 10.04 (Lucid) kernel >> 2.6.32-27 and persisting in 2.6.32-28. > > Not really. The newer kernels have code in them that does more > validity checks than previous kernels, so older kernels would have > erroneously and silently returned unlinked files to xfsdump and have > them backed up. IOWs, you'd never notice such a corruption with > xfsdump. On the new kernel, xfsdump gets an EINVAL error to such > occurrences, which it should have in the first place. > >> And there is one other person who confirmed this xfsdump problem >> running Lucid with kernel 2.6.32-28. They reported their "me too" >> in the Ubuntu bug tracker. >> >> Could it be that 2.6.32-26 and prior managed to write something to >> disk corrupted, and the newer code is tripping on it? > > That's what I'm trying to find out. Or it could be something as > simple as your disk has had an undetected bit error that has flipped > a bit in the inode allocation btree. > Hi Dave, I am able to reproduce this on a system running Ubuntu 10.4 (2.6.32-28). I took a metadump of the filesystem and moved it to a system running 10.10 (2.6.35-25), and was able to successfully dump it there. Likewise it dumps fine on 2.6.38-rc1. So this suggests an issue with the Ubuntu 10.4 kernel. Bill _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs