linux-ext4 - [Bug 195561] Suspicious persistent EXT4-fs error: ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap

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]

Message-ID: <bug-195561-13602-LX2iprgMKw@https.bugzilla.kernel.org/>
Date:   Tue, 09 May 2017 05:01:03 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 195561] Suspicious persistent EXT4-fs error:
 ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block
 bitmap

https://bugzilla.kernel.org/show_bug.cgi?id=195561

--- Comment #28 from Andreas Dilger (adilger.kernelbugzilla@...ger.ca) ---
As Ted has mentioned a couple of times, you could try running make_ext4fs and
then immediately running "e2fsck -f /dev/XXXX" on the filesystem created by
make_ext4fs _before_ it is mounted by the kernel.  It is entirely possible that
make_ext4fs is creating a corrupted filesystem, and the kernel is detecting
this at runtime.  This would explain why the filesystem is corrupted in the
same way for all of the different devices.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.