lkml.org 
[lkml]   [2001]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectreplaying reiserfs journal and bad blocks (was: Re[3]: Basic reiserfs question)
NB> If you think it's RedHat, you probably are wrong - I use RH with reiserfs
NB> a long time (more than a year - 6.2, now 7.1), and never got a message about
NB> replaying journal if system was shut down correctly.

After just written that, I got a real problem. There was a power loss a few minutes ago,
and I think when hdd was active. Trying to boot 2.4.7 kernel I got a message about
replaying journal, then hdd error:

hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=84415, sector=36216

and kernel panic. Please note that I mount root read-write with this kernel.

Then I rebooted 2.2.19 kernel (which mounts root as read-only if that matters):

Checking ReiserFS transaction log (device 16:42) ...
Warning, log recovery starting on readonly filesystem
hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=84415, sector=36216
end_request: I/O error, dev 16:42 (hdd), sector 36216
Replayed 33 transactions in 6 seconds
Using r5 hash to sort names
...
ReiserFS version 3.5.32
VFS: Mounted root (reiserfs filesystem) readonly.

and system booted normally.
Now I rebooted back to 2.4.7 and everything seems to be OK.
So what to do now? Run badblocks? Change disk? Any suggestions?

Regards,
Nerijus


-
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 13:02    [W:0.158 / U:1.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site