From: Arjan van de Ven <arjan@infradead.org>
To: Christian Pernegger <pernegger@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: *Really* bad I/O latency with md raid5+dm-crypt+lvm
Date: Mon, 12 Oct 2009 07:26:42 -0700 [thread overview]
Message-ID: <20091012072642.3a06a271@infradead.org> (raw)
In-Reply-To: <bb145bd20910120701p70c176d9p85028da7afec094c@mail.gmail.com>
On Mon, 12 Oct 2009 16:01:58 +0200
Christian Pernegger <pernegger@gmail.com> wrote:
> [Please keep me CCed as I'm not subscribed to LKML]
>
> Summary: I was hoping to use a layered storage setup, namely lvm on
> dm-crypt on md raid5 for a new box I'm setting up, but that isn't
> looking so good since a single heavyish writer will monopolise any and
> all I/O on the "device". F. ex. while cp'ing a few GB of data from an
> external disk to the array it takes ~10sec to run ls and ~2min to
> start aptitude. Clueless attempts at a diagnosis below.
have you ran latencytop ?
next prev parent reply other threads:[~2009-10-12 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 14:01 Christian Pernegger
2009-10-12 14:26 ` Arjan van de Ven [this message]
2009-10-12 19:05 ` Christian Pernegger
2009-10-12 14:48 Tomasz Chmielewski
2009-10-12 17:37 ` Mike Galbraith
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=20091012072642.3a06a271@infradead.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pernegger@gmail.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
Powered by JetHome