From: Edward Shishkin <edward.shishkin@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: fsck.reiser4 query
Date: Sun, 03 Jul 2011 23:02:02 +0200 [thread overview]
Message-ID: <4E10D8CA.4090005@gmail.com> (raw)
In-Reply-To: <99758203da18f9de8e42eadebeadc4a8@mail.velocitynet.com.au>
On 06/28/2011 04:31 AM, doiggl@velocitynet.com.au wrote:
> Hello,
> I have some questions.
>
> 1. Is there any possibility of speeding up the command proocess #
> fsck.reiser4 --build-fs /dev/xxx
Yes, such possibility does exist.
Fsck can work faster if you have many subvolumes
per superblock (currently reiser4 supports only one
subvolume per superblock).
> Could the metadata be loaded into ram and processed their or is the
> process entirly disk bound by I/O ?
This is both, CPU and I/O bound.
The first one can be improved if we make fsck process
all subvolumes in parallel. The second one can be improved
if we map subvolumes to different physical (scsi) drives.
> 2. Also will there a reiser4-for-2.6.39.patch in the future ?
I hope so..
Thanks,
Edward.
prev parent reply other threads:[~2011-07-03 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 2:31 fsck.reiser4 query doiggl
2011-07-03 21:02 ` Edward Shishkin [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=4E10D8CA.4090005@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).