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] EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32
Date: Tue, 11 Aug 2015 18:16:09 +0000	[thread overview]
Message-ID: <bug-89621-13602-VvjMyunzWm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89621-13602@https.bugzilla.kernel.org/>

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

--- Comment #17 from Theodore Tso <tytso@mit.edu> ---
John, are you willing to give us a lot more details about your set up?  
Hardware, software, details of the host OS, details of the guest OS, what is
the workload where the problem is happening, etc?

And it might be helpful if you opened a separate bug which we use exclusively
for tracking your particular issue.   One of the things which is often
disastrous, and why I've largely given up on Ubuntu's launchpad, is when
multiple people assume that the problem that they are seeing is the same as
everyone else's. when in fact they could be separate bugs, or one of the bugs
could be a hardware problem, etc.

Then when one person doesn't give details about their hardware because they saw
someone else already had, it makes finding the problems even harder.

One thing to keep in mind when we are talking about problems found in the guest
OS is that misconfigurations at the host OS level can be indistinguishable from
hardware problems.   So for example, depending on the caching policy used by
KVM in the host OS issues, it may be that cache flush commands in the guest OS
don't peculate down all the way down to the actual hardware platters.   Thus,
after a power fail event, even if everything is configured correctly at the
guest OS, it can result in an inconsistent file system image because the KVM /
the host OS didn't make sure everything got pushed to the disk after a journal
commit.

So knowing whether or not were any shutdowns caused either by KVM crashing, or
the host OS crashing, or the guest OS crashing, is all very important in trying
to debug things, because the error message reported simply means that there was
an inconsistency detected in the allocation bitmaps.   This can be caused by
any number of things --- which is why doctors hate it when someone asks them
what's wrong because "I have a cough" at a social occasion, and then someone
else chimes in, "well, my grandfather had a cough right before he was diagnosed
with terminal lung cancer"...

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

  parent reply	other threads:[~2015-08-11 18:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 12:28 [Bug 89621] New: EXT4-fs error (device dm-1): ext4_mb_release_inode_pa:3773: group 24089, free 34, pa_free 32 bugzilla-daemon
2014-12-13  3:36 ` [Bug 89621] " 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 [this message]
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-VvjMyunzWm@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).