All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13604] New: cascade of "mpage_da_map_blocks block allocation failed" errors
Date: Mon, 22 Jun 2009 20:25:32 GMT	[thread overview]
Message-ID: <bug-13604-13602@http.bugzilla.kernel.org/> (raw)

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

           Summary: cascade of "mpage_da_map_blocks block allocation
                    failed" errors
           Product: File System
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: bernie@codewiz.org
        Regression: No


While qemu was writing on a qcow2 image -- presumably a sparse, mmaped() file
--
the home partition filled up to the reserved block limit, and the kernel
started issuing a cascade of errors, making the system very unresponsive
for 30 seconds.

Eventually, the qemu process was killed with a SIGSEGV, but the system
was still unusable because every process attempting to read/write on /home
would lockup in an uninterruptable sleep state.

This is kernel-2.6.30-1.fc12.x86_64.

---cut---
Jun 22 20:49:03 localhost kernel: mpage_da_map_blocks block allocation failed
for inode 528965 at logical offset 607602 with max blocks 5 with error -28
Jun 22 20:49:03 localhost kernel: This should not happen.!! Data will be lost
Jun 22 20:49:03 localhost kernel: Total free blocks count 0
Jun 22 20:49:03 localhost kernel: Free/Dirty block details
Jun 22 20:49:03 localhost kernel: free_blocks=134303
Jun 22 20:49:03 localhost kernel: dirty_blocks=52621
Jun 22 20:49:03 localhost kernel: Block reservation details
Jun 22 20:49:03 localhost kernel: i_reserved_data_blocks=52465
Jun 22 20:49:03 localhost kernel: i_reserved_meta_blocks=156
Jun 22 20:49:03 localhost kernel: mpage_da_map_blocks block allocation failed
for inode 528965 at logical offset 608030 with max blocks 8 with error -28
Jun 22 20:49:03 localhost kernel: This should not happen.!! Data will be lost
Jun 22 20:49:03 localhost kernel: Total free blocks count 0
Jun 22 20:49:03 localhost kernel: Free/Dirty block details
Jun 22 20:49:03 localhost kernel: free_blocks=134303
Jun 22 20:49:03 localhost kernel: dirty_blocks=52621
Jun 22 20:49:03 localhost kernel: Block reservation details
Jun 22 20:49:03 localhost kernel: i_reserved_data_blocks=52465
Jun 22 20:49:03 localhost kernel: i_reserved_meta_blocks=156
Jun 22 20:49:09 localhost kernel: mpage_da_map_blocks block allocation failed
for inode 125287 at logical offset 4 with max blocks 1 with error -28
Jun 22 20:49:09 localhost kernel: This should not happen.!! Data will be lost
Jun 22 20:49:09 localhost kernel: Total free blocks count 0
Jun 22 20:49:09 localhost kernel: Free/Dirty block details
Jun 22 20:49:09 localhost kernel: free_blocks=134303
Jun 22 20:49:09 localhost kernel: dirty_blocks=52624
Jun 22 20:49:09 localhost kernel: Block reservation details
Jun 22 20:49:09 localhost kernel: i_reserved_data_blocks=1
Jun 22 20:49:09 localhost kernel: i_reserved_meta_blocks=2
Jun 22 20:52:36 localhost libvirtd: 20:52:36.573: warning :
qemudDispatchSignalEvent:362 : Shutting down on signal 15
---cut---

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

             reply	other threads:[~2009-06-22 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 20:25 bugzilla-daemon [this message]
2009-08-11 11:00 ` [Bug 13604] cascade of "mpage_da_map_blocks block allocation failed" errors bugzilla-daemon
2009-09-17 14:44 ` bugzilla-daemon
2009-09-17 15:51 ` bugzilla-daemon
2010-03-15 20:22 ` 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-13604-13602@http.bugzilla.kernel.org/ \
    --to=bugzilla-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 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.