linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12478] New: Infinite loop printing "__find_get_block_slow() failed." on accessing intentionally corrupted ext4 fs
Date: Sun, 18 Jan 2009 09:09:17 -0800 (PST)	[thread overview]
Message-ID: <bug-12478-13602@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=12478

           Summary: Infinite loop printing "__find_get_block_slow() failed."
                    on accessing intentionally corrupted ext4 fs
           Product: File System
           Version: 2.5
     KernelVersion: 2.6.29-rc2 + the patches for #12430
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: sliedes@cc.hut.fi


Hardware Environment: qemu x86
Software Environment: Minimal Debian sid/unstable
Problem Description:

Accessing the attached intentionally corrupted ext4 filesystem causes a
seemingly infinite (at least _very_ long) loop where kernel floods dmesg with
these messages:

[   67.126302] __find_get_block_slow() failed. block=4294967296, b_blocknr=0
[   67.126609] b_state=0x00000020, b_size=1024
[   67.126798] device blocksize: 1024
[   67.126972] __find_get_block_slow() failed. block=4294967296, b_blocknr=0
[   67.127244] b_state=0x00000020, b_size=1024
[   67.127415] device blocksize: 1024
[   67.127573] __find_get_block_slow() failed. block=4294967296, b_blocknr=0
[   67.127844] b_state=0x00000020, b_size=1024
... ad infinitum

Steps to reproduce:

1. bunzip2 the attached filesystem image
2. mount hdb.153 /mnt -t ext4 -o loop,errors=continue
3. rm -rf /mnt >&/dev/null


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2009-01-18 17:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 17:09 bugme-daemon [this message]
2009-01-18 17:10 ` [Bug 12478] Infinite loop printing "__find_get_block_slow() failed." on accessing intentionally corrupted ext4 fs bugme-daemon
2009-01-18 17:14 ` bugme-daemon
2009-05-19 18:32 ` bugzilla-daemon
2009-05-19 18:32 ` 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-12478-13602@http.bugzilla.kernel.org/ \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.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).