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: Thu, 28 May 2015 01:22:48 +0000 [thread overview]
Message-ID: <bug-89621-13602-Gk6HE9Q5Js@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 #12 from Theodore Tso <tytso@mit.edu> ---
Ah, never mind; the "debian 3.16.0" kernel is actually based on 3.16.7-ckt9 --
at least, the latest version of debian 3.16.0. You'd have to specify exactly
what version of the "debian 3.16.0" kernel to know for sure. (But this is why
many upstream kernel developers don't try to support distro kernels. It's hard
to see what commits might or might not be in a particular kernel distro.)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-05-28 1:22 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 [this message]
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-Gk6HE9Q5Js@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).