public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy
Date: Tue, 05 Aug 2014 05:06:17 +0000	[thread overview]
Message-ID: <bug-42723-13602-ej6RWuhm2F@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-42723-13602@https.bugzilla.kernel.org/>

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

Zhiyong Wu <zwu.kernel@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zwu.kernel@gmail.com

--- Comment #21 from Zhiyong Wu <zwu.kernel@gmail.com> ---
When trying to upgrade my deabian 7.5 box to 7.6 with "apt-get upgrade", i also
met this issue recently. And i checked its source and found that commit
b0dd6b70f0fd had been applied to my box kernel.

[ 35.500785] EXT4-fs (xvda1): re-mounted. Opts: errors=remount-ro,barrier=0
[ 35.526502] loop: module loaded
[ 36.367517] RPC: Registered named UNIX socket transport module.
[ 36.367520] RPC: Registered udp transport module.
[ 36.367521] RPC: Registered tcp transport module.
[ 36.367523] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 36.378239] FS-Cache: Loaded
[ 36.393865] FS-Cache: Netfs 'nfs' registered for caching
[ 36.405048] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 38.196190] EXT4-fs error (device xvda1): ext4_mb_generate_buddy:739: group
33, 9127 clusters in bitmap, 9143 in gd
[ 38.198208] Aborting journal on device xvda1-8.
[ 38.201249] EXT4-fs (xvda1): Remounting filesystem read-only
[ 38.202165] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4507:
Journal has aborted
[ 38.203509] EXT4-fs error (device xvda1): ext4_journal_start_sb:327: Detected
aborted journal
[ 38.207454] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4507:
Journal has aborted
[ 38.210148] EXT4-fs error (device xvda1) in ext4_ext_remove_space:2779:
Journal has aborted
[ 38.212614] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4507:
Journal has aborted
[ 38.215156] EXT4-fs error (device xvda1) in ext4_ext_truncate:4420: Journal
has aborted
[ 38.217590] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4507:
Journal has aborted
[ 38.220327] EXT4-fs error (device xvda1) in ext4_orphan_del:2110: Journal has
aborted
[ 38.227881] EXT4-fs error (device xvda1) in ext4_reserve_inode_write:4507:
Journal has aborted

# uname -a
Linux AY140708130459758e83Z 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64
GNU/Linux

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

  parent reply	other threads:[~2014-08-05  5:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 23:10 [Bug 42723] New: EXT4-fs error: ext4_mb_generate_buddy bugzilla-daemon
2012-02-10  1:09 ` [Bug 42723] " bugzilla-daemon
2012-02-20 12:12 ` bugzilla-daemon
2012-04-16  0:21 ` bugzilla-daemon
2012-05-09 18:03 ` bugzilla-daemon
2012-05-14  4:55 ` bugzilla-daemon
2012-10-29 20:25 ` bugzilla-daemon
2012-10-30 20:07 ` bugzilla-daemon
2012-10-30 20:55 ` bugzilla-daemon
2012-10-31  0:53 ` bugzilla-daemon
2012-11-02 15:20 ` bugzilla-daemon
2012-11-02 16:17 ` bugzilla-daemon
2012-11-02 16:43 ` bugzilla-daemon
2012-11-02 16:45 ` bugzilla-daemon
2012-11-02 16:56 ` bugzilla-daemon
2013-03-05  0:18 ` bugzilla-daemon
2013-06-01  9:22 ` bugzilla-daemon
2014-07-05  8:28 ` bugzilla-daemon
2014-07-05  8:41 ` bugzilla-daemon
2014-07-05 13:53 ` bugzilla-daemon
2014-07-06 19:42 ` bugzilla-daemon
2014-08-05  5:06 ` bugzilla-daemon [this message]
2014-08-05  9:13 ` bugzilla-daemon
2014-08-05 12:38 ` bugzilla-daemon
2014-08-06  3:45 ` bugzilla-daemon
2014-08-21  9:21 ` 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-42723-13602-ej6RWuhm2F@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