[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-89621-13602-HHFUboNHQT@https.bugzilla.kernel.org/>
Date: Thu, 28 May 2015 00:27:29 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 89621] EXT4-fs error (device dm-1):
ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32
https://bugzilla.kernel.org/show_bug.cgi?id=89621
--- Comment #11 from Theodore Tso <tytso@....edu> ---
Why are you still using v3.16.0? The latest 3.16 kernel is v3.16.7. I
believe the bug in question was fixed in a backport that first showed up in
v3.16.2:
commit 868be28e321b764da29592cfd9fd659434e823aa
Author: Theodore Ts'o <tytso@....edu>
Date: Wed Jul 30 22:17:17 2014 -0400
ext4: fix ext4_discard_allocated_blocks() if we can't allocate the pa
struct
commit 86f0afd463215fc3e58020493482faa4ac3a4d69 upstream.
If there is a failure while allocating the preallocation structure, a
number of blocks can end up getting marked in the in-memory buddy
bitmap, and then not getting released. This can result in the
following corruption getting reported by the kernel:
EXT4-fs error (device sda3): ext4_mb_generate_buddy:758: group 1126,
12793 clusters in bitmap, 12729 in gd
In that case, we need to release the blocks using mb_free_blocks().
Tested: fs smoke test; also demonstrated that with injected errors,
the file system is no longer getting corrupted
Google-Bug-Id: 16657874
Signed-off-by: "Theodore Ts'o" <tytso@....edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
--
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