From: Theodore Ts'o <tytso@mit.edu>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Matteo Croce <technoboy85@gmail.com>,
David Jander <david@protonic.nl>,
linux-ext4@vger.kernel.org
Subject: Re: ext4: journal has aborted
Date: Tue, 1 Jul 2014 11:58:12 -0400 [thread overview]
Message-ID: <20140701155812.GD2775@thunk.org> (raw)
In-Reply-To: <53B2A47F.90903@samsung.com>
On Tue, Jul 01, 2014 at 09:07:27PM +0900, Jaehoon Chung wrote:
> Hi,
>
> i have interesting for this problem..Because i also found the same problem..
> Is it Journal problem?
>
> I used the Linux version 3.16.0-rc3.
>
> [ 3.866449] EXT4-fs error (device mmcblk0p13): ext4_mb_generate_buddy:756: group 0, 20490 clusters in bitmap, 20488 in gd; block bitmap corrupt.
> [ 3.877937] Aborting journal on device mmcblk0p13-8.
> [ 3.885025] Kernel panic - not syncing: EXT4-fs (device mmcblk0p13): panic forced after error
This message means that the file system has detected an inconsistency
--- specifically, that the number of blocks marked as in use in the
allocation bbitmap is different from what is in the block group
descriptors.
The file system has been marked to force a panic after an error, at
which point e2fsck will be able to repair the inconsistency.
What's not clear is *how* the why this happened. It can happen simply
because of a hardware problem. (In particular, not all mmc flash
devices handle power failures gracefully.) Or it could be a cosmic,
ray, or it might be a kernel bug.
Normally I would chalk this up to a hardware bug, bug it's possible
that it is a kernel bug. If people can reliably reproduce the problem
where no power failures or other unclean shutdowns were involved
(since the last time file system has been checked using e2fsck) then
that would be realy interesting.
We should probably also change the message so the message is a bit
more understanding to people who aren't ext4 developers.
- Ted
next prev parent reply other threads:[~2014-07-01 15:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:30 ext4: journal has aborted Matteo Croce
2014-07-01 6:26 ` David Jander
2014-07-01 8:00 ` Matteo Croce
2014-07-01 8:42 ` Darrick J. Wong
2014-07-01 8:55 ` Matteo Croce
2014-07-02 13:49 ` Dmitry Monakhov
2014-07-03 13:43 ` Theodore Ts'o
2014-07-03 14:15 ` David Jander
2014-07-03 14:46 ` Theodore Ts'o
2014-07-03 14:57 ` Dmitry Monakhov
2014-07-03 14:58 ` Dmitry Monakhov
2014-07-04 9:40 ` David Jander
2014-07-04 10:17 ` Dmitry Monakhov
2014-07-04 11:28 ` David Jander
2014-07-04 12:20 ` Theodore Ts'o
2014-07-04 12:38 ` Dmitry Monakhov
2014-07-04 13:45 ` David Jander
2014-07-04 18:45 ` Theodore Ts'o
2014-07-04 22:46 ` Dave Chinner
2014-07-05 2:30 ` Dmitry Monakhov
2014-07-05 20:36 ` Theodore Ts'o
2014-07-07 12:17 ` David Jander
2014-07-07 15:53 ` Theodore Ts'o
2014-07-07 22:31 ` Darrick J. Wong
2014-07-07 22:56 ` Theodore Ts'o
2014-07-10 18:57 ` Eric Whitney
2014-07-10 20:01 ` Darrick J. Wong
2014-07-10 21:31 ` Matteo Croce
2014-07-10 22:32 ` Theodore Ts'o
2014-07-11 0:13 ` Darrick J. Wong
2014-07-11 0:45 ` Eric Whitney
2014-07-11 8:50 ` Jaehoon Chung
2014-07-11 11:43 ` Theodore Ts'o
2014-07-15 6:31 ` David Jander
2014-07-10 23:29 ` Azat Khuzhin
2014-07-04 11:04 ` Jaehoon Chung
2014-07-04 11:32 ` David Jander
2014-07-01 12:07 ` Jaehoon Chung
2014-07-01 13:50 ` David Jander
2014-07-01 15:58 ` Theodore Ts'o [this message]
2014-07-01 16:14 ` Lukáš Czerner
2014-07-01 16:36 ` Eric Whitney
2014-07-02 8:34 ` Matteo Croce
2014-07-02 10:17 ` David Jander
2014-07-02 10:19 ` Matteo Croce
2014-07-03 17:14 ` Eric Whitney
2014-07-03 23:17 ` Theodore Ts'o
2014-07-04 20:48 ` Eric Whitney
2014-07-02 9:44 ` David Jander
2014-07-01 9:02 ` Darrick J. Wong
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=20140701155812.GD2775@thunk.org \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=david@protonic.nl \
--cc=jh80.chung@samsung.com \
--cc=linux-ext4@vger.kernel.org \
--cc=technoboy85@gmail.com \
/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).