Arch Linux

vesz

Member

Registered: 2009-02-16

Posts: 10

ext4 - "Journal has aborted"? [SOLVED]

Hi, recently made all my partitions use ext4 instead of ext3. Now I might soon find that I'll be regretting it

Excerpt from dmesg:

ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
end_request: I/O error, dev sda, sector 55051824
Aborting journal on device sda2:8.
ata1: EH complete
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ext4_abort called.
EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted
EXT4-fs error (device sda2) in ext4_dirty_inode: Journal has aborted
mpage_da_map_blocks block allocation failed for inode 164698 at logical offset 47 with max blocks 4 with error -30
This should not happen.!! Data will be lost
ext4_da_writepages: jbd2_start: 1024 pages, ino 164698; err -30
Pid: 20, comm: pdflush Tainted: P           2.6.29-ARCH #1
Call Trace:
 [<ffffffffa00b2ea1>] ext4_da_writepages+0x491/0x4c0 [ext4]
 [<ffffffffa00b42f0>] ext4_da_get_block_write+0x0/0x190 [ext4]
 [<ffffffff802a0170>] do_writepages+0x20/0x40
 [<ffffffff802eb7af>] __writeback_single_inode+0xaf/0x4c0
 [<ffffffff8026805a>] debug_mutex_add_waiter+0x5a/0x90
 [<ffffffff802ec166>] generic_sync_sb_inodes+0x356/0x4c0
 [<ffffffff802ec48d>] writeback_inodes+0x4d/0xe0
 [<ffffffff802a02e6>] wb_kupdate+0xa6/0x130
 [<ffffffff802a12e3>] pdflush+0x163/0x240
 [<ffffffff802a0240>] wb_kupdate+0x0/0x130
 [<ffffffff802a1180>] pdflush+0x0/0x240
 [<ffffffff80259787>] kthread+0x47/0x90
 [<ffffffff8020d95a>] child_rip+0xa/0x20
 [<ffffffff80259740>] kthread+0x0/0x90
 [<ffffffff8020d950>] child_rip+0x0/0x20
EXT4-fs error (device sda2) in ext4_reserve_inode_write: Journal has aborted

Might have given you too much there, Anyway, is my disk broken or is it some kind of bug?

The effects are that my root file-system suddenly remounts itself to read-only. Upon reboot I need to do a manual fsck, it fixes some things
orphaned inode lists and a few other block related things. Then it works for a few minutes upon which everything repeats

// vesz

Last edited by vesz (2009-04-17 17:31:47)

ataraxia

Member

From: Pittsburgh

Registered: 2007-05-06

Posts: 1,553

Re: ext4 - "Journal has aborted"? [SOLVED]

Very possible your disk is dying. It might be your controller instead, though.

savagenator

Member

Registered: 2008-03-19

Posts: 21

Re: ext4 - "Journal has aborted"? [SOLVED]

I just got this exact problem, and was about to start a new thread when I did a dmesg | grep ext4 and got

EXT4-fs error (device sda3): ext4_journal_start_sb: Detected aborted journal

I'm not sure it is a bad disk because my disk is running 3 ext3 partitions and 1 ext4 (root). None of the other file systems are detecting any problems.

EDIT:

Okay, I just fixed the problem. Holy Moly was that an intense ride!

Short story:

I simply used a different SATA port in my computer. It was the controller! Thank you for that hint! Then I fsck'ed my drive.

Long story:

After I posted this message it remount the drive. This time, it remounted and I couldn't read it. My computer basically did a good ol' rm -rf on itself by disconnecting the drive. After a reboot, it didn't even boot. Something about waiting for signal. I then booted into the Arch 2009.02 cd and proceeded to try to mount, then fsck the drive. That did not work. In fact, fsck just errored out when trying to recover the journal. Then I tried system rescue cd 1.1.6. Also failed the same way.

I stood up off my chair, thought a bit, then changed the SATA port. DONE!

Last edited by savagenator (2009-04-16 17:37:06)

vesz

Member

Registered: 2009-02-16

Posts: 10

Re: ext4 - "Journal has aborted"? [SOLVED]

I guess I'll try to do the same, I converted the partition back to ext3 and it's working without any problems atm. None of the other disks are complaining(they are still ext4) so might just be the port.

Thanks

forkboy

Member

From: Blackpool, England

Registered: 2005-09-03

Posts: 74

Re: ext4 - "Journal has aborted"? [SOLVED]

I know this thread is old now but vesz did you get this sorted? I've started having the same problem.