From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1Edy9M-0008I9-Nu for garchives@archives.gentoo.org; Sun, 20 Nov 2005 22:59:09 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jAKMwtZT023462; Sun, 20 Nov 2005 22:58:55 GMT Received: from smtp010.tiscali.dk (smtp010.tiscali.dk [212.54.64.103]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jAKMwsKO027961 for ; Sun, 20 Nov 2005 22:58:54 GMT Received: from kloeri (62.79.108.22.adsl.ynoe.tiscali.dk [62.79.108.22]) by smtp010.tiscali.dk (8.12.10/8.12.10) with SMTP id jAKMwp8n006698 for ; Sun, 20 Nov 2005 23:58:51 +0100 (MET) Received: by kloeri (sSMTP sendmail emulation); Sun, 20 Nov 2005 23:58:51 +0100 From: "Bryan Ăstergaard" Date: Sun, 20 Nov 2005 23:58:51 +0100 To: gentoo-alpha@lists.gentoo.org Subject: Re: [gentoo-alpha] Aborted Journal Message-ID: <20051120225851.GA9967@kloeri> References: <4380E979.5070206@videotron.ca> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-alpha@gentoo.org Reply-to: gentoo-alpha@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Disposition: inline In-Reply-To: <4380E979.5070206@videotron.ca> User-Agent: Mutt/1.5.8i Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id jAKMwtZi023462 X-Archives-Salt: 0c95b094-865b-42d1-b020-43c8daac695e X-Archives-Hash: fd56854d605c88b5d56b9e2175203c0e On Sun, Nov 20, 2005 at 04:24:09PM -0500, Jean-S=C3=A9bastien Guay wrote: > Hello, >=20 > I was doing an emerge --sync on my Alpha XL 366 today, and it started=20 > saying that it couldn't write on the drive because it was read-only.=20 > Looking at dmesg, I saw this : >=20 > sd 0:0:0:0: SCSI error: return code =3D 0x70000 > end_request: I/O error, dev sda, sector 10060048 >=20 > [... lots of other messages like the previous two lines, where only the= =20 > sector changes ...] >=20 Looks like normal hardware errors. I'd make sure to backup any important data and change the drive. > 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 jo= urnal > Remounting filesystem read-only > EXT3-fs error (device sda7) in ext3_reserve_inode_write: Journal has ab= orted > __journal_remove_journal_head: freeing b_committed_data >=20 > [... a couple more lines like the previous one ...] Normal behavior in case of harddrive errors. There's a slight chance this could be caused by a bad driver but then it'd probably always have been a problem. >=20 >=20 > What could cause this? I've had this problem before, and if I remember=20 > correctly it lead to a complete data loss on the drive (argh). This tim= e=20 > it seems not to have happened, because I have rebooted the machine and=20 > everything seems ok. But what could cause this, and what can I do to=20 > prevent it (short of not running emerge --sync :-) ? >=20 Regards, Bryan =C3=98stergaard --=20 gentoo-alpha@gentoo.org mailing list