public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Frey <cdfrey@foursquare.net>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 filesystem corruption in user mode linux
Date: Mon, 27 Sep 2010 20:48:55 -0400	[thread overview]
Message-ID: <20100928004855.GA28669@foursquare.net> (raw)
In-Reply-To: <AANLkTi=iSSffp-48g0XAOYBSnodAsEh20j2EtHW=4Egt@mail.gmail.com>

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 <cdfrey@foursquare.net> 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


  parent reply	other threads:[~2010-09-28  0:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  4:14 ext3 filesystem corruption in user mode linux Chris Frey
2010-09-24  6:05 ` Chris Frey
2010-09-24  6:44   ` Chris Frey
2010-09-27 21:04     ` richard -rw- weinberger
2010-09-27 21:18       ` Chris Frey
2010-09-27 21:25         ` richard -rw- weinberger
2010-09-27 21:26           ` Chris Frey
2010-09-27 21:59             ` Chris Frey
     [not found]               ` <AANLkTinmCxYrjdYoDUE6+zg1i1QSJxt5ngN84FrjWJaj@mail.gmail.com>
     [not found]                 ` <20100927221225.GA22343@foursquare.net>
     [not found]                   ` <AANLkTi=iSSffp-48g0XAOYBSnodAsEh20j2EtHW=4Egt@mail.gmail.com>
2010-09-28  0:48                     ` Chris Frey [this message]
2010-09-27 20:54 ` Chris Frey
2010-09-27 21:00   ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100928004855.GA28669@foursquare.net \
    --to=cdfrey@foursquare.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox