From: "Tõnis Bramanis" <tonis@elkdata.ee>
To: Joseph Glanville <joseph.glanville@orionvm.com.au>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: Limit I/O for individual disks of VM
Date: Wed, 28 Sep 2011 10:48:09 +0300 [thread overview]
Message-ID: <4E82D139.2060100@elkdata.ee> (raw)
In-Reply-To: <CAOzFzEhcJDy6K=ffUi8Y=VGBmo_pSqFSR50grhgp49s=7C-OZw@mail.gmail.com>
If i run the exact same kernel without Xen and test the i/o, it won't crash.
I just tried to look up an old post to refer it to You and seems it has
been updated just yesterday with a fix:
http://xen.1045712.n5.nabble.com/Xen-4-1-3ware-9690SA-rejecting-I-O-to-offline-device-td3208156.html
Still, i will try to change the raid controller and see what happens then.
Regards,
Tõnis Bramanis
On 28.09.2011 10:38, Joseph Glanville wrote:
> Hi,
>
> To add to the above it looks like you have a device driver or hardware
> issue with your harddrive or raid controller.
> I/O ratelimiting might hide the symptoms but not correct the problem.
> After you have addressed that you can look at implementing rate limiting
> via the methods described below:
>
> cgroups blk-io controller:
> You can find documentation etc in the linux git repo at
> /documentation/cgroups/blkio-controller.txt
>
> dm-ioband:
> Wiki is here http://sourceforge.net/apps/trac/ioband/wiki/dm-ioband
>
> Both of these are external to Xen for the reasons outlined by previous
> posts.
>
> Kind regards,
> Joseph.
>
> 2011/9/28 Jeremy Fitzhardinge <jeremy@goop.org <mailto:jeremy@goop.org>>
>
> On 09/27/2011 11:25 PM, Tõnis Bramanis wrote:
> > Hello
> >
> > and thank You for the answer. Has anyone of You tried to limit i/o on
> > the VMs?
> >
> > I have about 40 containers and when the i/o gets too high, the host
> > will crash with this error:
> > [23959.739698] sd 4:0:0:0: rejecting I/O to offline device
> > 5 [23959.771158] Buffer I/O error on device dm-0, logical
> block 40259
> >
> > This is not a support request! I am just referring why i would
> like to
> > limit the disks i/o.
>
> I think that IO error is a real problem that you should try to solve,
> rather than work around it by rate-limiting IO.
>
> J
>
> >
> > Regards,
> > Tõnis Bramanis
> >
> > On 27.09.2011 22 <tel:27.09.2011%2022>:58, Jeremy Fitzhardinge wrote:
> >> On 09/27/2011 01:33 AM, Tõnis Bramanis wrote:
> >>> Hello!
> >>>
> >>> Will disk i/o limiting be added in any future versions? I see it in
> >>> the 4.0 feature requests, but not in any changelogs.
> >>
> >> I think the hope is that we can use the generic Linux mechanisms for
> >> this rather than having to add anything Xen-specific.
> >>
> >> J
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com <mailto:Xen-devel@lists.xensource.com>
> http://lists.xensource.com/xen-devel
>
>
>
>
> --
> */
> Founder | Director | VP Research
> Orion Virtualisation Solutions/* | www.orionvm.com.au
> <http://www.orionvm.com.au/> | Phone: 1300 56 99 52 | Mobile: 0428 754 846
next prev parent reply other threads:[~2011-09-28 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 8:33 Limit I/O for individual disks of VM Tõnis Bramanis
2011-09-27 19:58 ` Jeremy Fitzhardinge
2011-09-28 6:25 ` Tõnis Bramanis
2011-09-28 6:35 ` Jeremy Fitzhardinge
2011-09-28 6:38 ` Tõnis Bramanis
2011-09-28 7:38 ` Joseph Glanville
2011-09-28 7:48 ` Tõnis Bramanis [this message]
2011-09-28 9:42 ` Andrew Cooper
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=4E82D139.2060100@elkdata.ee \
--to=tonis@elkdata.ee \
--cc=jeremy@goop.org \
--cc=joseph.glanville@orionvm.com.au \
--cc=xen-devel@lists.xensource.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.