Hi Andreas, thanks for your reply. On Monday 03 June 2002 11:37 pm, Andreas Dilger wrote: > On Jun 03, 2002 23:04 +0200, Duncan Sands wrote: > > While compiling two kernels and untarring a third, my root fs was > > remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): > > ^^^ r/o I presume... Sure, sorry about that. > > EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 > > Aborting journal on device ide0(3,2). > > ext3_abort called > > This is a known error, and I thought a fix was submitted by Andrew > and/or Stephen. It should not cause a filesystem error just because > the filesystem was full. > > > Rebooting didn't help: the journal aborted immediately. > > Hmm, running e2fsck is needed to fix an aborted journal - the in-kernel > journal recovery code isn't smart enough to do this. You _do_ run > e2fsck on your filesystems at boot, right? Just because you are using > ext3 is no reason to turn off e2fsck. e2fsck is smart enough that if > you are running ext3 it will only do journal recovery and not do a full > filesystem check unless there is a filesystem error (like you have > here), or if the "time since last checked" has elapsed. If you don't > like the latter behaviour, see tune2fs man page on how to change this > (via -c and -I options). Here is what happened (from memory): (1) the filesystem problem (journal abort) is detected (2) e2fsck is run (3) kjournald starts (4) the journal is aborted Repeat (by rebooting) as many times as you like... All the best and thanks again, Duncan.
