All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: reiserfs-list@namesys.com
Subject: fsck 0.5.5 time
Date: Fri, 18 Jun 2004 14:01:12 +0300	[thread overview]
Message-ID: <20040618110112.GG4990@nysv.org> (raw)

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


             reply	other threads:[~2004-06-18 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 11:01 mjt [this message]
2004-06-18 11:55 ` fsck 0.5.5 time Vladimir V. Saveliev
2004-06-18 12:14   ` mjt
2004-06-18 12:20   ` Vitaly Fertman
2004-06-18 12:29     ` mjt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040618110112.GG4990@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.