From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759936Ab0I1AtJ (ORCPT ); Mon, 27 Sep 2010 20:49:09 -0400 Received: from nic.NetDirect.CA ([216.16.235.2]:58509 "EHLO rubicon.netdirect.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751373Ab0I1AtI (ORCPT ); Mon, 27 Sep 2010 20:49:08 -0400 X-Originating-Ip: 216.16.235.2 Date: Mon, 27 Sep 2010 20:48:55 -0400 From: Chris Frey To: richard -rw- weinberger Cc: linux-kernel@vger.kernel.org Subject: Re: ext3 filesystem corruption in user mode linux Message-ID: <20100928004855.GA28669@foursquare.net> References: <20100924060557.GA21238@foursquare.net> <20100924064446.GA22588@foursquare.net> <20100927211842.GA19667@foursquare.net> <20100927212650.GA20386@foursquare.net> <20100927215941.GA20458@foursquare.net> <20100927221225.GA22343@foursquare.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 28, 2010 at 01:35:09AM +0200, richard -rw- weinberger wrote: > On Tue, Sep 28, 2010 at 12:12 AM, Chris Frey wrote: > > I'm using a mixture of the following to test.  The errors happen > > during the 'rm'. > > > >        Direct copy: > >                (cd dir && tar cjf - portage) | tar xjf - ; rm -rf portage > > > >        Hostfs copy: > >                tar xjf /mnt/hostfs/portage-latest.tar.bz2 ; rm -rf portage > > > >        Network copy: > >                ssh remote "cat portage-latest.tar.bz2" | tar xjf - ; rm -rf portage > > > > With these tests, I'm almost guessing that it might be some missed IRQs > > or something in the guest, since files that are corrupt often contain > > all zeros, which would match the sparse filesystem images I'm using. > > Hmm, something really nasty is going one here. > I can reproduce this issue using ext2, ext3 and reiserfs as UML root filesystem. > It seems to be a block layer issue. > Tomorrow I'll have a close look at the issue using my openSUSE setup. > So far I've used your Gentoo image. I've also seen the issue with a Ubuntu guest as well. So far, I don't think it matters what OS is in the guest. Thanks for reproducing the error! - Chris