From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org
Subject: Re: kernel BUG at fs/ext4/extents.c:2766!
Date: Wed, 7 Mar 2012 18:29:49 +0100 [thread overview]
Message-ID: <20120307172949.GA5799@alea.gnuu.de> (raw)
In-Reply-To: <CAGBYx2bc7mgYGm3gTbJt2Lhd7UbvW59fk7JPDs9dVqPJ-9OB3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hallo Yank,
Yongqiang Yang hat am Wed 07. Mar, 18:59 (+0800) geschrieben:
> On Wed, Mar 7, 2012 at 9:14 AM, Jörg Sommer <joerg@alea.gnuu.de> wrote:
> > Hi,
> >
> > I've got this Oops after I've created a file that filled up the
> > filesystem.
> >
> > [ 852.407974] ------------[ cut here ]------------
> > [ 852.412105] kernel BUG at /build/buildd-linux-2.6_3.2.9-1-powerpc-xXyGnW/linux-2.6-3.2.9/debian/build/source_powerpc_none/fs/ext4/extents.c:2766!
> Hi,
>
> Could this be reproduced?
I can't belive it, yes, it's possible. I haven't expected this. I can
provide you a filesystem image that you can boot and reproduce it
yourself, if you have qemu installed. The image is 620MB. I can also
create an image with e2image from the broken filesystem.
Regards, Jörg.
--
And 1.1.81 is officially BugFree(tm), so if you receive any bug-reports
on it, you know they are just evil lies.
(Linus Torvalds)
[-- Attachment #2: Digital signature http://en.wikipedia.org/wiki/OpenPGP --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-03-07 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 1:14 kernel BUG at fs/ext4/extents.c:2766! Jörg Sommer
2012-03-07 10:59 ` Yongqiang Yang
2012-03-07 17:29 ` Jörg Sommer [this message]
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=20120307172949.GA5799@alea.gnuu.de \
--to=joerg@alea.gnuu.de \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xiaoqiangnk@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;
as well as URLs for NNTP newsgroup(s).