fsck 0.5.5 time

fsck 0.5.5 time

[mjt]

Hi

How long is the expected time for fsck to run?
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.

Are there any risks in using the read-only mounted /home/ while fscking?

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_.

Thanks a million!

-- 
mjt

Re: fsck 0.5.5 time

[Vladimir V. Saveliev]

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!
> 

Re: fsck 0.5.5 time

[mjt]

On Fri, Jun 18, 2004 at 03:55:23PM +0400, Vladimir V. Saveliev wrote:

>Can you just leave it to work? When you will be back - everything will 
>be done

I would love to, but the point lies in taking the desktop with me and doing
work from elsewhere. Actually a LAN Party but I will spend most my time
there working.

>>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

I'm not doing anything heavy with it, as most software wants to write
something to the disk. Watching a music DVD and using ssh is now
going on.

>How do you run fsck.reiser4?

With -v --fix

FSCK: Node (8134683), item (0), [29:0:2a] (stat40): needs pset member (6) set
to
(stat40). Added. 
FSCK: Directory [104d1:61767300000000:104d2] (dir40), node [2064563], item
[6],
unit [10]: entry has wrong offset 
[104d2:0(NAME):1616c6976616c74:696f736968746565:30a1a50eff86ab5c]. Should be 
[104d2:0(NAME):1616c6976616c74:696f736968746565:7b6737fc14d277c]. 

Besides that there is no output. I don't really know what else there could
be, maybe something like the weird data in --build-sb[1] or anything
that lets the end-user know something is actually happening.

Or maybe I'm the only one who wants verbosity to be real verbose :)

[1] 
What does that --build-sb info mean?
Coordinates in the tree or something? But they fluctuate at what looks close
to random.

Thanks for the reply!

-- 
mjt

Re: fsck 0.5.5 time

[Vitaly Fertman]

Hello,

On Friday 18 June 2004 15:55, Vladimir V. Saveliev wrote:
> Hello
>
> Markus Törnqvist wrote:
> > Hi
> >
> > How long is the expected time for fsck to run?

depends on the speed of your hardware, kind of corruptions, 
fsck options, many things.

> 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?

should be ok, if you are talking about the plugin set that is added into 
the root. 

> > 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_.

yes, you are right, there will be some progress on semtanic pass also, 
it has not been implemented yet. 

> How do you run fsck.reiser4?
>
> > Thanks a million!

-- 
Thanks,
Vitaly Fertman

Re: fsck 0.5.5 time

[mjt]

On Fri, Jun 18, 2004 at 04:20:25PM +0400, Vitaly Fertman wrote:
>> > How long is the expected time for fsck to run?
>depends on the speed of your hardware, kind of corruptions, 
>fsck options, many things.

Yeah, I was just hoping for some rough estimate of a clean filesystem
with a some benchmark setup :)

Well, it's not that critical.

>> > Are there any risks in using the /home/ read-write without the stat data
>> > extensions, or whatever --fix fixes?
>should be ok, if you are talking about the plugin set that is added into 
>the root. 

Well, I guess I am :)
I couldn't remember exactly what the new addition that wanted --fix was,
but I thought I remembered it was statdata extensions.

>yes, you are right, there will be some progress on semtanic pass also, 
>it has not been implemented yet. 

Hooray! I owe you a beer :)

-- 
mjt