From: Oleg Drokin <green@namesys.com>
To: myciel <myciel@dotcom.pl>
Cc: reiserfs-list@namesys.com
Subject: Re: fsck in background?
Date: Tue, 8 Apr 2003 18:28:24 +0400 [thread overview]
Message-ID: <20030408182824.A17750@namesys.com> (raw)
In-Reply-To: <3E929926.3020705@dotcom.pl>
Hello!
On Tue, Apr 08, 2003 at 11:40:54AM +0200, myciel wrote:
> >We have a patch that significantly speeds things up.
> >In the similar case 28+ years estimated for pass 0 turned into 208 hours
> >total
> >operations after speedup patch was applied.
> >We plan to include it into reiserfsprogs 3.6.6-pre1, but if you need that
> >urgently,
> >tell us.
> thanks for answer, so please let me know where I can get the patch.
It is now included into reiserfsprogs 3.6.6-pre1, you can get it from
ftp://ftp.namesys.com/pub/reiserfsprogs/pre/reiserfsprogs-3.6.6-pre1.tar.gz
> And I have another question - again maybe this is not good idea, but:
> if we can fsck of snapshot (without error fixing), so maybe
> it would be possible to store output data from readonly fscking
> and just feed reiserfsck in rw mode to avoid scanning whole fs during
> repairing,
> and fix only corrupted places found during readonly scan?
Well, this is still pretty complicated.
Nodes might have been shifted around compared to the snapshot we did the checking on.
Bye,
Oleg
next prev parent reply other threads:[~2003-04-08 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 10:30 fsck in background? myciel
2003-03-31 10:46 ` Oleg Drokin
2003-03-31 17:14 ` Hans Reiser
2003-03-31 17:27 ` Oleg Drokin
2003-03-31 17:54 ` Vitaly Fertman
2003-03-31 18:54 ` Hans Reiser
2003-04-05 5:37 ` Andreas Dilger
2003-04-07 17:06 ` Hans Reiser
2003-04-08 9:40 ` myciel
2003-04-08 14:28 ` Oleg Drokin [this message]
2003-03-31 10:47 ` Robin H. Johnson
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=20030408182824.A17750@namesys.com \
--to=green@namesys.com \
--cc=myciel@dotcom.pl \
--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.