From: mjt@nysv.org
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: fsck 0.5.5 time
Date: Fri, 18 Jun 2004 15:29:01 +0300 [thread overview]
Message-ID: <20040618122901.GI4990@nysv.org> (raw)
In-Reply-To: <200406181620.25609.vitaly@namesys.com>
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
prev parent reply other threads:[~2004-06-18 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 11:01 fsck 0.5.5 time mjt
2004-06-18 11:55 ` Vladimir V. Saveliev
2004-06-18 12:14 ` mjt
2004-06-18 12:20 ` Vitaly Fertman
2004-06-18 12:29 ` mjt [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=20040618122901.GI4990@nysv.org \
--to=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@namesys.com \
--cc=vs@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.