[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-72401-13602@https.bugzilla.kernel.org/>
Date: Tue, 18 Mar 2014 08:37:28 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.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
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@...nel-bugs.osdl.org
Reporter: zweiustc@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists