Re: journal aborted, system read-only

[Gene Heskett]

On Thursday 16 September 2004 02:34, Valdis.Kletnieks@xxxxxx wrote:
>On Mon, 13 Sep 2004 16:12:59 BST, "Stephen C. Tweedie" said:
>> Well, we really need to see _what_ error the journal had
>> encountered to be able to even begin to diagnose it.  But
>> 2.6.9-rc1-mm3 and -mm4 had a bug in the journaling introduced by
>> low-latency work on the checkpoint code; can you try -mm5 or back
>> out
>> "journal_clean_checkpoint_list-latency-fix.patch" and try again?
>
>I just got bit by the 'journal aborted' problem under -rc1-mm5, so
> it looks like that particular bug wasn't at fault here (also, I
> started seeing the problem under -mm2, so that's another point
> against that theory...)
>
Thanks Valdis, now I don't feel quite so lonely in this camp. :-)

[...]

>This happened about 4 minutes into a 'tar cf - | (cd && tar xf -)'
> pipeline to clone a work copy of the -rc1-mm5 source tree (it got
> about 408M through the 543M before it blew up)....

Humm, it happened to me while amdump was running, and amdump uses tar.
My tar version is 1.13-25.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.26% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/