linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 24 Apr 2017 16:50:08 +0000	[thread overview]
Message-ID: <bug-195561-13602-OrKexrDqV2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195561-13602@https.bugzilla.kernel.org/>

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

Andreas Dilger (adilger.kernelbugzilla@dilger.ca) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@dilg
                   |                            |er.ca

--- Comment #7 from Andreas Dilger (adilger.kernelbugzilla@dilger.ca) ---
Given that the same corruption is happening across different block devices, it
points to something other than the block device going bad.  It might be a bug
in the ext4 code, or some other kernel code that is corrupting the memory
(unlikely), or a userspace process that is clobbering this block.

It would be worthwhile to save a copy of the corrupted bitmap block for further
analysis.  It may be possible to identify what is overwriting that block by
looking at the content.

Collect "dumpe2fs -h" output for the filesystem, so we can see what features
are enabled.  Collect "dd if=/dev/sda1 of=/tmp/block.dat bs=4k count=1
skip=557056" and then dump it via "od -Ax4 -tx4 -a /tmp/block.dat".

You could also potentially add a tracepoint or run blktrace to see which
processes are writing to this block.  It should only be the jbd2 thread.

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

  parent reply	other threads:[~2017-04-24 16:50 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 [this message]
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
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-OrKexrDqV2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).