From: Chris Frey <cdfrey@foursquare.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ext3 filesystem corruption in user mode linux
Date: Fri, 24 Sep 2010 02:05:57 -0400 [thread overview]
Message-ID: <20100924060557.GA21238@foursquare.net> (raw)
In-Reply-To: <20100924041410.GA18040@foursquare.net>
On Fri, Sep 24, 2010 at 12:14:10AM -0400, Chris Frey wrote:
> If I do some heavy CPU and disk work in the guest, something like this:
>
> # (cd /usr && tar cjf - portage) | tar xjf -
> # rm -rf portage
>
> Then the filesystem corrupts itself, giving errors like the following
> in dmesg, during the rm:
>
> EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 51715
Update:
So far I have been unable to make 2.6.32.21 corrupt its filesystem
when running as the UML kernel (Host 2.6.35.4, UML 2.6.32.21)
When running UML 2.6.33.7, I get similar errors:
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21397
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13257
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13257
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21403
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 21403
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13262
EXT3-fs error (device ubda): ext3_lookup: deleted inode referenced: 13262
EXT3-fs error (device ubda): htree_dirblock_to_tree: bad entry in directory #13269: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs (ubda): warning: empty_dir: bad directory (dir #13269) - no `.' or `..'
EXT3-fs (ubda): warning: ext3_rmdir: empty directory has nlink!=2 (3)
If anyone wants me to test a specific UML kernel, please let me know.
- Chris
next prev parent reply other threads:[~2010-09-24 6:06 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 [this message]
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
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=20100924060557.GA21238@foursquare.net \
--to=cdfrey@foursquare.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.