From: Eric Sandeen <sandeen@redhat.com>
To: Matteo Croce <matteo@openwrt.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
Date: Wed, 20 May 2009 20:19:14 -0500 [thread overview]
Message-ID: <4A14AC12.4000108@redhat.com> (raw)
In-Reply-To: <40101cc30905201635t6af2586bne1acbc77216628ee@mail.gmail.com>
Matteo Croce wrote:
> When launching a web browser in normal desktop usage, I get this and
> the disk mounted read only:
>
> [ 1101.535101] EXT4-fs error (device sda1) in
> ext4_reserve_inode_write: Journal has aborted
Anything before that? I'd think you'd get a message when the journal
aborts.
> [ 1101.535114] Remounting filesystem read-only
> [ 1101.535622] EXT4-fs error (device sda1) in
> ext4_reserve_inode_write: Journal has aborted
> [ 1101.535637] EXT4-fs error (device sda1) in ext4_dirty_inode:
> Journal has aborted
> [ 1101.535669] mpage_da_map_blocks block allocation failed for inode
> 1867 at logical offset 0 with max blocks 1 with error -30
> [ 1101.535681] This should not happen.!! Data will be lost
Hm this is probably a bad followon to the filesystem shutting down, and
delalloc data having nowhere to go...
-Eric
> [ 1101.535703] ext4_da_writepages: jbd2_start: 1024 pages, ino 1867; err -30
> [ 1101.535716] Pid: 26, comm: pdflush Not tainted 2.6.29.1 #12
> [ 1101.535724] Call Trace:
> [ 1101.535744] [<c038602c>] ? printk+0x18/0x1c
> [ 1101.535862] [<c01e5999>] ext4_da_writepages+0x409/0x430
> [ 1101.535879] [<c01e7670>] ? ext4_da_get_block_write+0x0/0x210
> [ 1101.535893] [<c01e5590>] ? ext4_da_writepages+0x0/0x430
> [ 1101.535907] [<c0174f6e>] do_writepages+0x2e/0x50
> [ 1101.535921] [<c01b4748>] __writeback_single_inode+0x88/0x500
> [ 1101.535936] [<c0122957>] ? set_next_entity+0x97/0x180
> [ 1101.535950] [<c01b4f73>] generic_sync_sb_inodes+0x283/0x410
> [ 1101.535963] [<c01b52b7>] writeback_inodes+0x47/0xd0
> [ 1101.535975] [<c01750e2>] wb_kupdate+0xb2/0x120
> [ 1101.535988] [<c01761d2>] pdflush+0x112/0x1d0
> [ 1101.536000] [<c0175030>] ? wb_kupdate+0x0/0x120
> [ 1101.536160] [<c01760c0>] ? pdflush+0x0/0x1d0
> [ 1101.536173] [<c0144e6c>] kthread+0x3c/0x70
> [ 1101.536184] [<c0144e30>] ? kthread+0x0/0x70
> [ 1101.536198] [<c0103cdb>] kernel_thread_helper+0x7/0x1c
> [ 1101.536417] journal commit I/O error
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-21 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 23:35 EXT4-fs error in ext4_reserve_inode_write: Journal has aborted Matteo Croce
2009-05-21 1:19 ` Eric Sandeen [this message]
2009-05-22 8:31 ` Matteo Croce
2009-05-22 11:10 ` Theodore Tso
2009-05-22 12:23 ` Matteo Croce
2009-05-22 15:11 ` Eric Sandeen
2009-05-22 12:37 ` Eric Sandeen
2009-05-22 13:25 ` Matteo Croce
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=4A14AC12.4000108@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=matteo@openwrt.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).