linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Noobadmin <centos.admin-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: CentOS mailing list
	<centos-IFYaIzF+flcdnm+yROfE0A@public.gmane.org>,
	linux-raid <linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Possible to use multiple disk to bypass I/O wait?
Date: Thu, 9 Jun 2011 17:24:23 +0800	[thread overview]
Message-ID: <BANLkTimFOaJoMnwid1F+ghVwkBgJi2FymQ@mail.gmail.com> (raw)

I'm trying to resolve an I/O problem on a CentOS 5.6 server. The
process basically scans through Maildirs, checking for space usage and
quota. Because there are hundred odd user folders and several 10s of
thousands of small files, this sends the I/O wait % way high. The
server hits a very high load level and stops responding to other
requests until the crawl is done.

I am wondering if I add another disk and symlink the sub-directories
to that, would that free up the server to respond to other requests
despite the wait on that disk?

Alternatively, if I mdraid mirror the existing disk, would md be smart
enough to read using the other disk while the first's tied up with the
first process?

             reply	other threads:[~2011-06-09  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  9:24 Emmanuel Noobadmin [this message]
2011-06-09 10:19 ` Possible to use multiple disk to bypass I/O wait? Mathias Burén
2011-06-09 16:15   ` Emmanuel Noobadmin
2011-06-09 12:06 ` Nagilum
     [not found] ` <BANLkTimFOaJoMnwid1F+ghVwkBgJi2FymQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-06-09 19:06   ` Steve Thompson

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=BANLkTimFOaJoMnwid1F+ghVwkBgJi2FymQ@mail.gmail.com \
    --to=centos.admin-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=centos-IFYaIzF+flcdnm+yROfE0A@public.gmane.org \
    --cc=linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).