From: Hans Reiser <reiser@namesys.com>
To: Oleg Drokin <green@namesys.com>
Cc: Jeff Breidenbach <jbreiden@parc.com>, reiserfs-list@namesys.com
Subject: Re: disk or reiserfs problem?
Date: Thu, 05 Jun 2003 17:20:09 +0400 [thread overview]
Message-ID: <3EDF4389.7090308@namesys.com> (raw)
In-Reply-To: <20030603053336.GC8667@namesys.com>
Oleg Drokin wrote:
>Hello!
>
>On Mon, Jun 02, 2003 at 01:00:36PM -0700, Jeff Breidenbach wrote:
>
>
>
>>Incidentally, during the restoration I find that cp is
>>giving a throughput of about 1 MB/s when copying from
>>harddrive to harddrive. Both source and destination disks
>>use reiserfs and hdparm -tT reports about 50MB/s read rate.
>>Is a 1MB/s throughput expected when copying many small files?
>>(There is a lot of data involved, so I probably have a couple
>>of days to ponder the question.)
>>
>>
>
>Copying lots of small files can take lots of time just because you
>cannot read those in order they are stored on disk platter. And you do not know
>the order most probably. So the end result is the disk does constant seeking and
>the speed is reduced. If you know the order in which files were written (e.g. alphabetically),
>then you can read them in the same order (plain "cp -R . somedir" will read files in readdir order)
>I am not very sure what can be done in such a case if you do not know the order in
>which files were written. Perhaps if you copy the mounted backup drive to /dev/zero
>(e.g. dd if=/dev/hdb1 /dev/zero bs=1024k count=500 (replace 500 with the half of your RAM
>in megabytes) and you have large enough RAM, there is a chance that this will cache
>enough data to keep stuff moving more quickly.
>
>Bye,
> Oleg
>
>
>
>
Your performance will improve after the restoration though....
--
Hans
next prev parent reply other threads:[~2003-06-05 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 20:07 disk or reiserfs problem? Jeff Breidenbach
2003-05-29 5:45 ` Oleg Drokin
2003-06-02 18:36 ` Hans Reiser
2003-06-02 20:00 ` Jeff Breidenbach
2003-06-03 5:33 ` Oleg Drokin
2003-06-03 17:49 ` Prereading block device doesn't help filesystems Mike Fedyk
2003-06-03 18:19 ` Chris Mason
2003-06-05 13:20 ` Hans Reiser [this message]
2003-06-05 13:38 ` disk or reiserfs problem? Nikita Danilov
2003-06-03 5:23 ` Oleg Drokin
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=3EDF4389.7090308@namesys.com \
--to=reiser@namesys.com \
--cc=green@namesys.com \
--cc=jbreiden@parc.com \
--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.