* EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
@ 2009-05-20 23:35 Matteo Croce
2009-05-21 1:19 ` Eric Sandeen
0 siblings, 1 reply; 8+ messages in thread
From: Matteo Croce @ 2009-05-20 23:35 UTC (permalink / raw)
To: linux-ext4
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
[ 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
[ 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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
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
2009-05-22 8:31 ` Matteo Croce
0 siblings, 1 reply; 8+ messages in thread
From: Eric Sandeen @ 2009-05-21 1:19 UTC (permalink / raw)
To: Matteo Croce; +Cc: linux-ext4
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
2009-05-21 1:19 ` Eric Sandeen
@ 2009-05-22 8:31 ` Matteo Croce
2009-05-22 11:10 ` Theodore Tso
2009-05-22 12:37 ` Eric Sandeen
0 siblings, 2 replies; 8+ messages in thread
From: Matteo Croce @ 2009-05-22 8:31 UTC (permalink / raw)
To: Eric Sandeen; +Cc: linux-ext4
the HD seems to reset soon.
can it be an hardware problem?
On Thu, May 21, 2009 at 3:19 AM, Eric Sandeen <sandeen@redhat.com> wrote:
> 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
>
>
--
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
2009-05-22 8:31 ` Matteo Croce
@ 2009-05-22 11:10 ` Theodore Tso
2009-05-22 12:23 ` Matteo Croce
2009-05-22 12:37 ` Eric Sandeen
1 sibling, 1 reply; 8+ messages in thread
From: Theodore Tso @ 2009-05-22 11:10 UTC (permalink / raw)
To: Matteo Croce; +Cc: Eric Sandeen, linux-ext4
On Fri, May 22, 2009 at 10:31:17AM +0200, Matteo Croce wrote:
> the HD seems to reset soon.
> can it be an hardware problem?
I'm not sure what you mean by "the HD seems to reset soon"?
If there was a "Journal has aborted" error, there must have been some
some other ext4 or jbd2 reported problem earlier in the log that
caused the journal to have aborted. Could you search your log file
for anything beforehand mentioning "ext4", "EXT4-fs", or "jbd2", or
"journal"?
Thanks,
- Ted
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
2009-05-22 11:10 ` Theodore Tso
@ 2009-05-22 12:23 ` Matteo Croce
2009-05-22 15:11 ` Eric Sandeen
0 siblings, 1 reply; 8+ messages in thread
From: Matteo Croce @ 2009-05-22 12:23 UTC (permalink / raw)
To: Theodore Tso; +Cc: Eric Sandeen, linux-ext4
SCSI error, status {DRDY}
sort of
On Fri, May 22, 2009 at 1:10 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Fri, May 22, 2009 at 10:31:17AM +0200, Matteo Croce wrote:
>> the HD seems to reset soon.
>> can it be an hardware problem?
>
> I'm not sure what you mean by "the HD seems to reset soon"?
>
> If there was a "Journal has aborted" error, there must have been some
> some other ext4 or jbd2 reported problem earlier in the log that
> caused the journal to have aborted. Could you search your log file
> for anything beforehand mentioning "ext4", "EXT4-fs", or "jbd2", or
> "journal"?
>
> Thanks,
>
> - Ted
>
>
--
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
2009-05-22 8:31 ` Matteo Croce
2009-05-22 11:10 ` Theodore Tso
@ 2009-05-22 12:37 ` Eric Sandeen
2009-05-22 13:25 ` Matteo Croce
1 sibling, 1 reply; 8+ messages in thread
From: Eric Sandeen @ 2009-05-22 12:37 UTC (permalink / raw)
To: Matteo Croce; +Cc: linux-ext4
Matteo Croce wrote:
> the HD seems to reset soon.
> can it be an hardware problem?
It can be, it'd be easier for me to tell you if you could provide any
messages prior to the remount messages, as I'd requested.
If you see things like ATA errors or resets, then yes, it's likely a
hardware problem.
But without actual information, I just have to guess....
-Eric
> On Thu, May 21, 2009 at 3:19 AM, Eric Sandeen <sandeen@redhat.com> wrote:
>> 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
>>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
2009-05-22 12:37 ` Eric Sandeen
@ 2009-05-22 13:25 ` Matteo Croce
0 siblings, 0 replies; 8+ messages in thread
From: Matteo Croce @ 2009-05-22 13:25 UTC (permalink / raw)
To: Eric Sandeen; +Cc: linux-ext4
I haven't the syslog now, but it was normal messages, not ATA related or errors
On Fri, May 22, 2009 at 2:37 PM, Eric Sandeen <sandeen@redhat.com> wrote:
> Matteo Croce wrote:
>> the HD seems to reset soon.
>> can it be an hardware problem?
>
> It can be, it'd be easier for me to tell you if you could provide any
> messages prior to the remount messages, as I'd requested.
>
> If you see things like ATA errors or resets, then yes, it's likely a
> hardware problem.
>
> But without actual information, I just have to guess....
>
> -Eric
>
>> On Thu, May 21, 2009 at 3:19 AM, Eric Sandeen <sandeen@redhat.com> wrote:
>>> 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
>>>
>
>
--
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
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2009-05-22 15:11 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
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).