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, 16 Dec 2014 14:55:57 +0000 [thread overview]
Message-ID: <bug-89621-13602-nz5dmfjDdz@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 #7 from Theodore Tso <tytso@mit.edu> ---
OK, so vis-a-vis case #1, it looks like the fsck didn't take.
Dec 3 11:04:26 cedric kernel: [ 1.440438] EXT4-fs (dm-0): mounting ext3
file system using the ext4 subsystem
Dec 3 11:04:26 cedric kernel: [ 1.468114] EXT4-fs (dm-0): mounted
filesystem with ordered data mode. Opts: (null)
Dec 3 11:04:26 cedric kernel: [ 6.139705] EXT4-fs (dm-0): re-mounted. Opts:
(null)
Dec 3 11:04:26 cedric kernel: [ 6.311768] EXT4-fs (dm-0): re-mounted. Opts:
errors=remount-ro
Dec 3 11:09:11 cedric kernel: [ 302.048065] EXT4-fs (dm-0): error count since
last fsck: 3
Dec 3 11:09:11 cedric kernel: [ 302.048102] EXT4-fs (dm-0): initial error at
time 1417556618: ext4_mb_release_inode_pa:3773
Dec 3 11:09:11 cedric kernel: [ 302.048105] EXT4-fs (dm-0): last error at
time 1417596801: ext4_remount:4853
I'm not exactly sure what time zone your system messages are in, but e2fsck
1.42.5 (I assume you're using e2fsprogs from debian stable?) will clear the
error stats, and time 1417596801 is:
% TZ=GMT date -d @1417596801
Wed Dec 3 08:53:21 GMT 2014
Either that, or maybe the raid system is acting up and writes aren't going to
both halves, or something weird like that? Can you do me a favor and
configure a handful of VM's that ***don't*** use MD RAID, just so we can rule
out funny business on that score?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-12-16 14:56 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 [this message]
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-nz5dmfjDdz@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).