Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alpha
Lists: gentoo-alpha: < Prev By Thread Next > < Prev By Date Next >
To: Gentoo-Alpha Mailing List <gentoo-alpha@g.o>
From: Jean-Sébastien Guay <jean_seb@...>
Subject: Aborted Journal
Date: Sun, 20 Nov 2005 16:24:09 -0500

I was doing an emerge --sync on my Alpha XL 366 today, and it started 
saying that it couldn't write on the drive because it was read-only. 
Looking at dmesg, I saw this :

sd 0:0:0:0: SCSI error: return code = 0x70000
end_request: I/O error, dev sda, sector 10060048

[... lots of other messages like the previous two lines, where only the sector changes ...]

Aborting journal on device sda7.
EXT3-fs error (device sda7) in ext3_new_inode: Journal has aborted
ext3_abort called.
EXT3-fs error (device sda7): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sda7) in ext3_reserve_inode_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data

[... a couple more lines like the previous one ...]

What could cause this? I've had this problem before, and if I remember 
correctly it lead to a complete data loss on the drive (argh). This time 
it seems not to have happened, because I have rebooted the machine and 
everything seems ok. But what could cause this, and what can I do to 
prevent it (short of not running emerge --sync :-) ?

Thanks in sdvance,


Jean-Sébastien Guay   jean_seb@...

gentoo-alpha@g.o mailing list

Re: Aborted Journal
-- Bryan �tergaard
Lists: gentoo-alpha: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
2.6 kernel on Alpha ?
Next by thread:
Re: Aborted Journal
Previous by date:
Re: 2.6 kernel on Alpha ?
Next by date:
Re: Aborted Journal

Updated Jun 17, 2009

Summary: Archive of the gentoo-alpha mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.