Re: fsck 0.5.5 time

["Vladimir V. Saveliev" <vs@namesys.com>]

Hello

Markus Törnqvist wrote:
> Hi
> 
> How long is the expected time for fsck to run?

It may take several hours. Especially, because, I guess, there was not 
much work done in its performance

> I did --fix on my root partition, which is around 32 gigabytes and it
> took nearly an hour, maybe. The fact that I cancelled --build-sb to run
> --fix sort of messed up my measurements.
> 
> However, my /home/mjt/ is 102G with about 50 free.
> 
> Time interval: Fri Jun 18 12:41:09 2004 - Fri Jun 18 12:41:14 2004
> 
> That's about the only time reference I have. The time is now about 14:00.
> 
> How should it take?
> The thing is, I'm leaving with my desktop computer in a few hours, so I
> may have to cancel and restart later. I also don't want to re-do this, as
> I'll be busy until Sunday with more pressing matters.
> 
Can you just leave it to work? When you will be back - everything will 
be done

> Are there any risks in using the read-only mounted /home/ while fscking?
> 
If it mounts - you can probably use it. Just do not be surprised with 
EIO, ENOENT, etc

> Are there any risks in using the /home/ read-write without the stat data
> extensions, or whatever --fix fixes?
> 
> Is there some more verbosity coming into fsck, just to let me know it's
> actually doing something? Sure, I follow it with top -d1 but that's
> not too reassuring. Maybe some counter of how many {kilo,mega,giga}bytes
> left to check or some tree numbers or _anything_.
> 

How do you run fsck.reiser4?

> Thanks a million!
>