From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 72401] New: EXT4-fs error (device sdf1): ext4_mb_complex_scan_group:1786: group 11890254 free clusters as per group info. But got 256 blocks
Date: Tue, 18 Mar 2014 08:37:28 +0000 [thread overview]
Message-ID: <bug-72401-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=72401
Bug ID: 72401
Summary: EXT4-fs error (device sdf1):
ext4_mb_complex_scan_group:1786: group 11890254 free
clusters as per group info. But got 256 blocks
Product: File System
Version: 2.5
Kernel Version: 3.2
Hardware: IA-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: zweiustc@gmail.com
Regression: No
EXT4-fs error (device sdf1): ext4_mb_complex_scan_group:1786: group 11890254
free clusters as per group info. But got 256 blocks
EXT4-fs error (device sdf1): ext4_mb_complex_scan_group:1786: group 11890494
free clusters as per group info. But got 496 blocks
EXT4-fs error (device sdf1): ext4_mb_complex_scan_group:1786: group 125222297
free clusters as per group info. But got 2304 blocks
The server log showed that the num of free blocks diffs from the result we
calculate from the extent tree. I have not found how to reproduce it but it
happened on several servers. I am trying to reproduce it and look into the
code. I wonder anyone once confronted such a case before.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-03-19 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 8:37 bugzilla-daemon [this message]
2014-03-18 8:38 ` [Bug 72401] EXT4-fs error (device sdf1): ext4_mb_complex_scan_group:1786: group 11890, 254 free clusters as per group info. But got 256 blocks bugzilla-daemon
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=bug-72401-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 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).