> Chris Mason <mason@suse.com> writes:
>> > reiserfs: checking transaction log (device 03:04) ...
>> > Warning, log replay starting on readonly filesystem
>> >
>>
>> Here, reiserfs is telling you that it has started replaying transactions
>> in the log. You should also have a reiserfs message telling you how many
>> transactions it replayed, and how long it took. Do you have that
>> message?
>
> Nope. I rebooted with Alt-SysRQ+B after some while (aprox more than 30
> sec, normally reiserfs replay is taking ~5 sec (pre9)). I wasn't so
> patient. I could test it before I'll go from work to home.
>
Ok, depending on the metadata load before the crash, replay can take 30
seconds or more. You usually have to try to generate that many metadata
changes, something like creating 100,000 tiny files or directories.
Compiling with CONFIG_REISERFS_CHECK turned on will give you more details
about the log replay.
Or, perhaps DMA is now off on your IDE drive, making everything slower.
Regardless, rebooting in the middle of log replay is safe. Those
transactions will just be replayed again on the next boot.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/