From: Mike Galbraith <efault@gmx.de>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-kernel@vger.kernel.org, pernegger@gmail.com, arjan@infradead.org
Subject: Re: *Really* bad I/O latency with md raid5+dm-crypt+lvm
Date: Mon, 12 Oct 2009 19:37:56 +0200 [thread overview]
Message-ID: <1255369076.7162.3.camel@marge.simson.net> (raw)
In-Reply-To: <4AD341B2.6000704@wpkg.org>
On Mon, 2009-10-12 at 16:48 +0200, Tomasz Chmielewski wrote:
> > 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.
>
> Did you try running strace to see where ls pauses?
>
> Did you try running latencytop (and generally, top/htop while doing your
> tests)?
>
>
> (...)
>
> > Anyway, as soon as I copy something to the array or create a larger
> > (upwards of a few hundred MiB) tar archive the box becomes utterly
> > unresponsive until that job is finished. Even on the local console the
> > completion time for a simple ls or cat is of the order of tens of
> > seconds, just forget about launching emacs.
> > Now I know that people have been ranting about desktop responsiveness
> > for a while but that was very much an abstract thing for me until now.
>
> I think the above (big latency when doing some bigger IO) is a general
> Linux problem.
It would be interesting to test latest -rc. Though it may prove to be
unrelated. the symptoms sound very much like a recent thread wrt writers
starving readers.
-Mike
next prev parent reply other threads:[~2009-10-12 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 14:48 *Really* bad I/O latency with md raid5+dm-crypt+lvm Tomasz Chmielewski
2009-10-12 17:37 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-12 14:01 Christian Pernegger
2009-10-12 14:26 ` Arjan van de Ven
2009-10-12 19:05 ` Christian Pernegger
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=1255369076.7162.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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 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.