From: Hans Reiser <reiser@namesys.com>
To: Julian Hall <jules@acris.co.uk>
Cc: reiserfs-list@namesys.com, Vitaly Fertman <vitaly@namesys.com>
Subject: Re: Typo in reiserfsck
Date: Wed, 11 Dec 2002 23:33:12 +0300 [thread overview]
Message-ID: <3DF7A108.6090507@namesys.com> (raw)
In-Reply-To: <3DF76F33.2030101@acris.co.uk>
Julian Hall wrote:
> While rebuilding my file system's tree today, I noticed this message:
>
> ####### Pass 1 #######
> Looking for allocable blocks .. fininshed
>
> And a quick comment: the program doesn't really give much indication
> of how long rebuilding the tree will take. When I started I certainly
> had no idea that it would take over 4 hours (it hasn't finished yet,
> but I think its getting close now...) to complete, and if I knew I
> would probably have left the operation until I had more time
> available. Read-only access to the file system would have been useful,
> but unfortunately that option was not left open to me by the time I
> realised that the operation would take so long...
>
>
>
>
Thanks for your correction. Vitaly, how about collecting a table of
statistics for completion time for various pieces of hardware, and
asking the user if he would like to see it before starting fsck?
prev parent reply other threads:[~2002-12-11 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 17:00 Typo in reiserfsck Julian Hall
2002-12-11 20:33 ` Hans Reiser [this message]
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=3DF7A108.6090507@namesys.com \
--to=reiser@namesys.com \
--cc=jules@acris.co.uk \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.