From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dd slow while reading on multipathing, writing is fast
Date: Wed, 09 Feb 2011 12:03:13 +0100 [thread overview]
Message-ID: <1297249393.29348.17.camel@zezette> (raw)
In-Reply-To: <638331349.4388161297176246800.JavaMail.root@tendai.telenet-ops.be>
On mar., 2011-02-08 at 15:44 +0100, bart.coninckx@telenet.be wrote:
> Hi all,
>
> something peculiar I cannot get my head round.
> I have a setup where a backup server connects to iSCSI LUNs over multipathing.
> While dd-ing to it, I get a spiffing 200 MB/sec, while reading it drops to 70 MB/sec. Local storage where I write the image onto is sufficiently fast.
>
> Do you think this is multipathing related? I'm running the latest version from source.
>
please send at least
- kernel version
- multipath tools version
- device map string
next prev parent reply other threads:[~2011-02-09 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <315312316.4387891297176180905.JavaMail.root@tendai.telenet-ops.be>
2011-02-08 14:44 ` dd slow while reading on multipathing, writing is fast bart.coninckx
2011-02-09 11:03 ` Christophe Varoqui [this message]
2011-02-09 11:22 ` Bryn M. Reeves
2011-02-10 19:48 ` Bart Coninckx
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=1297249393.29348.17.camel@zezette \
--to=christophe.varoqui@gmail.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox