linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 89621] New: EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32
Date: Fri, 12 Dec 2014 12:28:11 +0000	[thread overview]
Message-ID: <bug-89621-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 89621
           Summary: EXT4-fs error (device dm-1):
                    ext4_mb_release_inode_pa:3773: group 24089, free 34,
                    pa_free 32
           Product: File System
           Version: 2.5
    Kernel Version: 3.16
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: john@calva.com
        Regression: No

I've been getting this EXT4 error (on an ext3 filesystem) on two virtual
machines, running Debian kernel 3.16-0.bpo.2-amd64.

The stack is:

Host (3.16): Mdadm raid1
LVM
Guest (also 3.16): LVM2 volume, ext3 formatted

[    7.413209] EXT4-fs (dm-4): mounting ext3 file system using the ext4
subsystem
[    7.431191] EXT4-fs (dm-4): warning: maximal mount count reached, running
e2fsck is recommended
[    7.442501] EXT4-fs (dm-4): mounted filesystem with journalled data mode.
Opts: data=journal,errors=remount-ro
...
[957229.875900] EXT4-fs (dm-4): pa ffff88001f7ff980: logic 0, phys. 9176576,
len 128
[957229.878640] EXT4-fs error (device dm-4): ext4_mb_release_inode_pa:3773:
group 280, free 128, pa_free 127
[957229.881350] Aborting journal on device dm-4-8.
[957229.891273] EXT4-fs (dm-4): Remounting filesystem read-only
[957561.369731] EXT4-fs (dm-4): pa ffff880009f7b028: logic 0, phys. 9192448,
len 512
[957561.371926] EXT4-fs error (device dm-4): ext4_mb_release_inode_pa:3773:
group 280, free 512, pa_free 511
[957688.608554] EXT4-fs error (device dm-4): ext4_put_super:792: Couldn't clean
up the journal

This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772848

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

             reply	other threads:[~2014-12-12 12:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 12:28 bugzilla-daemon [this message]
2014-12-13  3:36 ` [Bug 89621] EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32 bugzilla-daemon
2014-12-15 11:57 ` bugzilla-daemon
2014-12-15 14:51 ` bugzilla-daemon
2014-12-15 15:21 ` bugzilla-daemon
2014-12-15 22:27 ` bugzilla-daemon
2014-12-16 11:46 ` bugzilla-daemon
2014-12-16 14:55 ` bugzilla-daemon
2015-05-21 19:01 ` bugzilla-daemon
2015-05-27  9:53 ` bugzilla-daemon
2015-05-27 10:01 ` bugzilla-daemon
2015-05-28  0:27 ` bugzilla-daemon
2015-05-28  1:22 ` bugzilla-daemon
2015-05-28  5:24 ` bugzilla-daemon
2015-05-28 10:35 ` bugzilla-daemon
2015-07-24 16:17 ` bugzilla-daemon
2015-08-11 15:15 ` bugzilla-daemon
2015-08-11 18:16 ` bugzilla-daemon
2015-08-11 21:11 ` bugzilla-daemon
2015-08-12  9:08 ` bugzilla-daemon
2015-08-12  9:12 ` bugzilla-daemon
2022-02-04 13:13 ` bugzilla-daemon
2022-02-07  9:34 ` 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-89621-13602@https.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 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).