From: WIMPy <WIMPy@yeti.dk>
To: linux-ext4@vger.kernel.org
Subject: Re: [dm-devel] can't recover ext4 on lvm from ext4_mb_generate_buddy:739: group 1687, 32254 clusters in bitmap, 32258 in gd
Date: Sat, 28 Jan 2012 04:53:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20120128T050950-718@post.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.1201061133140.6954@hs20-bc2-1.build.redhat.com
Mikulas Patocka <mpatocka <at> redhat.com> writes:
> The existence of a snapshot changes I/O completion times significantly, so
> it may be a race condition in ext4 that gets triggered which changed
> timings.
The idea that timing might cause issues on a FS is disturbing.
> > this is a problem which apparently occurred when the user went from
> > v3.1.5 to v3.2, so this looks likes 3.2 regression.)
I am on 3.2.0 as well.
It happened for me on a freshly created FS.
"mke2fs -j -O sparse_super -O dir_index -O extents -O filetype -O uninit_bg"
mounted with no additional options for the first time I got an
"EXT4-fs error (device md127): ext4_mb_generate_buddy:739: group 28671, 32765
clusters in bitmap, 32766 in gd"
after writing about 3TB of data.
I do not have RO snapshots as the OP, but my md sits on to of luks containers.
So we do have the device mapper in common.
Just for the records: Unlike the contents, the hardware is not new and did not
have any known issues.
Greetings,
WIMPy
next prev parent reply other threads:[~2012-01-28 6:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 10:37 can't recover ext4 on lvm from ext4_mb_generate_buddy:739: group 1687, 32254 clusters in bitmap, 32258 in gd Sander Eikelenboom
2012-01-05 13:21 ` Sander Eikelenboom
2012-01-05 14:45 ` Theodore Tso
2012-01-05 14:45 ` Theodore Tso
2012-01-05 14:52 ` Sander Eikelenboom
2012-01-05 14:52 ` Sander Eikelenboom
2012-01-05 15:46 ` Sander Eikelenboom
2012-01-05 15:46 ` Sander Eikelenboom
[not found] ` <4910694144.20120105171428@eikelenboom.it>
2012-01-05 18:15 ` Ted Ts'o
2012-01-05 20:04 ` Sander Eikelenboom
2012-01-05 20:04 ` Sander Eikelenboom
2012-01-05 20:45 ` Sander Eikelenboom
2012-01-05 20:45 ` Sander Eikelenboom
2012-01-05 21:31 ` Sander Eikelenboom
2012-01-05 21:31 ` Sander Eikelenboom
2012-01-05 22:43 ` Sander Eikelenboom
2012-01-05 22:43 ` Sander Eikelenboom
2012-01-06 16:40 ` [dm-devel] " Mikulas Patocka
2012-01-28 4:53 ` WIMPy [this message]
2012-01-28 8:14 ` WIMPy
2012-01-28 8:34 ` Andreas Dilger
2012-01-28 15:31 ` WIMPy
2012-01-28 21:04 ` WIMPy
2012-02-03 5:30 ` WIMPy
2012-04-12 6:45 ` Landry Minoza
2012-04-12 6:45 ` Landry Minoza
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 23:06 [dm-devel] " Tony Hoyle
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=loom.20120128T050950-718@post.gmane.org \
--to=wimpy@yeti.dk \
--cc=linux-ext4@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.