From: Theodore Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Linux Kernel Mailinlinux-ext4@vger.kernel.orgg List"
<linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: ext4fs error "ext4_mb_generate_buddy:741:group 16, 8160 clusters in bitmap, 4064 in gd" (with repro)
Date: Thu, 9 Aug 2012 13:06:40 -0400 [thread overview]
Message-ID: <20120809170640.GA6607@thunk.org> (raw)
In-Reply-To: <50238A29.3060808@redhat.com>
On Thu, Aug 09, 2012 at 12:00:09PM +0200, Paolo Bonzini wrote:
> Here is how to reproduce it. It happens during fstrim. I found other
> occurrences of the error in the mailing list, but they were not related
> to trim so they may be something different.
>
> modprobe scsi_debug dev_size_mb=256 lbpws=1
> dd if=/dev/zero of=/dev/sdb bs=1M
> fdisk /dev/sdb
> >> create a new partition accepting all defaults
> fdisk -lu /dev/sdb|tail -1
> >> should show: /dev/sdb1 57 524285 262114+ 83 Linux
>
> mkfs.ext4 /dev/sdb1
> mkdir test
> mount /dev/sdb1 test
> fstrim ./test
I can confirm that this accurately reproduces file system corruption
using a 3.5 kernel. It looks like some block allocation bitmap blocks
is getting trimmed when it shouldn't have been. Lukas, can you take a
look at this?
- Ted
next prev parent reply other threads:[~2012-08-09 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 10:00 ext4fs error "ext4_mb_generate_buddy:741:group 16, 8160 clusters in bitmap, 4064 in gd" (with repro) Paolo Bonzini
2012-08-09 17:06 ` Theodore Ts'o [this message]
2012-08-15 9:17 ` Lukáš Czerner
2012-08-16 14:28 ` Lukáš Czerner
2012-08-16 20:00 ` Theodore Ts'o
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=20120809170640.GA6607@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).