From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 195561] Suspicious persistent EXT4-fs error: ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap
Date: Tue, 09 May 2017 05:01:03 +0000 [thread overview]
Message-ID: <bug-195561-13602-LX2iprgMKw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195561-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=195561
--- Comment #28 from Andreas Dilger (adilger.kernelbugzilla@dilger.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.
next prev parent reply other threads:[~2017-05-09 5:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 2:40 [Bug 195561] New: Suspicious persistent EXT4-fs error (device sda1): ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap bugzilla-daemon
2017-04-24 2:41 ` [Bug 195561] " bugzilla-daemon
2017-04-24 2:42 ` bugzilla-daemon
2017-04-24 2:44 ` bugzilla-daemon
2017-04-24 2:52 ` bugzilla-daemon
2017-04-24 3:00 ` bugzilla-daemon
2017-04-24 3:01 ` [Bug 195561] Suspicious persistent EXT4-fs error: " bugzilla-daemon
2017-04-24 4:51 ` bugzilla-daemon
2017-04-24 16:50 ` bugzilla-daemon
2017-04-24 16:53 ` bugzilla-daemon
2017-04-25 15:22 ` bugzilla-daemon
2017-04-25 15:23 ` bugzilla-daemon
2017-04-25 15:24 ` bugzilla-daemon
2017-04-25 15:27 ` bugzilla-daemon
2017-04-25 15:29 ` bugzilla-daemon
2017-04-25 15:29 ` bugzilla-daemon
2017-04-25 15:31 ` bugzilla-daemon
2017-04-25 15:32 ` bugzilla-daemon
2017-04-25 23:13 ` bugzilla-daemon
2017-04-25 23:14 ` bugzilla-daemon
2017-04-25 23:16 ` bugzilla-daemon
2017-04-25 23:18 ` bugzilla-daemon
2017-04-25 23:19 ` bugzilla-daemon
2017-04-25 23:20 ` bugzilla-daemon
2017-04-26 15:11 ` bugzilla-daemon
2017-04-29 21:59 ` bugzilla-daemon
2017-04-30 2:59 ` bugzilla-daemon
2017-04-30 3:20 ` bugzilla-daemon
2017-05-03 8:17 ` bugzilla-daemon
2017-05-03 17:48 ` bugzilla-daemon
2017-05-09 3:20 ` bugzilla-daemon
2017-05-09 5:01 ` bugzilla-daemon [this message]
2017-05-09 16:10 ` bugzilla-daemon
2017-05-13 12:00 ` bugzilla-daemon
2017-05-14 4:14 ` bugzilla-daemon
2017-05-14 11:41 ` bugzilla-daemon
2017-05-14 14:56 ` bugzilla-daemon
2017-05-14 18:20 ` 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-195561-13602-LX2iprgMKw@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.