lkml.org 
[lkml]   [2004]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: journal aborted, system read-only
On Fri, 17 Sep 2004, Gene Heskett wrote:

> Thats the same conclusion I've since come to, Valdis. And, now that
> I've moved my /var to its own partition on another disk, that may
> have reduced the thrashing of that drive enough to stop the problem.
> At least I've had no more such occurances since I moved /var off
> of /. About 30.5 hours now according to the uptime display in
> gkrellm.

I've just experienced a very similar situation: I/O error, journal abort,
partition went read-only. Maybe it's completely unrelated, but by chance,
do you have some clipping jumper set on this disk so you depend on the
ide-stroke feature?

In my case this was the culprit. It's a 120GB disk in a box with old
crashing Award BIOS, so I've clipped it to 32GB. However I've missed the
fact since about 2.6.7 one has to set hda=stroke kernel parameter in order
to get the host protected area disabled. Therefore partitions starting
behind 32GB failed to mount.

In contrast, the partition which crosses the 32GB barrier was mounted
succesfully but later when trying to access beyond the limit I was seeing:

ide0: reset: success
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=110291109, high=6, low=9627813, sector=110291109
ide: failed opcode was: unknown
end_request: I/O error, dev hda, sector 110291109
EXT3-fs error (device hda7): ext3_get_inode_loc: unable to read inode block - inode=3883009, block=7766022
Aborting journal on device hda7.
ext3_abort called.
EXT3-fs error (device hda7): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only

Adding the hda=stroke kernel parameter solved the issue - forced fsck
showed no damage happened to the fs.

HTH,
Martin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:06    [W:0.373 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site