linux-ext4 - [Bug 89621] EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Dec 2014 14:51:12 +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 #3 from Theodore Tso <tytso@....edu> ---
Well, was this a one-time thing or can you easily reproduce this error?   The
problem is that almost anything can cause this --- bad memory, a wild pointer
derference coming from a proprietary video driver from Nvidia, etc.   And by
the time we get the ext4-error, basically what we have is the dead body lying
in the alley.   Where the bullet came from, and from what direction, and who
fired the gun, is not something that will be immediately evident; just that we
have a very specific kind of inconsistency between the allocation bitmap and
the block group summary statistics.  So in order to track it down, we need to
be able to try to isolate causes.   So for example, does the problem show up if
you use the latest bleeding edge kernel from mainline, etc.

-- 
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